CMS Made Simple Forums

It could be an ownership issue, which you may need to resolve with your host's help. There's also been a few instances where the opcache extension causes strange permission problems, you could try temporarily disabling it.

Not that I can recall, although it may have to be after the form_start tag. If that still doesn't work, clear the cache, and check your php error logs.

FEU 2.9 has some important information in the release notes: Note: By default you MUST add {cge_form_csrf} to the inside of all forms in FEU form templates or an error will be generated on form submission. You can disable this behaviour by using the cge_ignore_csrf config setting. See the CGEXtensio...

Check your user preferences to see which wywiwyg editor you have selected. Most likely it has reset to 'none' during the upgrade.

Easiest might be to use generic templates for the parts that are different, and keep both on the same master template. So something like this in your master template (possibly edited to work with your mobiledetect plugin): {if $mobile} {include file="cms_template:mymobiletemplate} {else} {inclu...

That looks like it's just a true or false to detect mobile based on the user agent string, nothing to do with the width. You don't have a meta viewport tab, so mobile devices will just shrink the page. Your css is detecting the size properly, as your "screen and (min-width: 1px) and (max-width:...

How are you checking the width, with media queries or javascript? What do you have in your <meta name="viewport" ...> tag? Are you using a framework?

Might be a good idea to share your template and/or a link to the site.

I'm not sure what you mean by the backend script folder. Are you looking for an automated utility to back up the site? There are one or two modules that will do this, but generally the backup procedure is simply: clear CMSMS cache tar.gz all of the files (using your host's file manager or shell) bac...

A version of CMSMS that old may not work on PHP 7.x, so it's possible your host upgraded it without your knowledge. Not 100% certain that's it, but it's possible. You may also just want to try clearing the site cache. You also need to make upgrading CMSMS a priority. If it's not something you're com...

Yep, and the detail one as well. Anywhere it's not getting eval'd and you want it to.

If you take a look at the default News templates, you'll see a comment like: {* note, for security purposes, incase News articles can come from untrused sources, we do not pass the summary or content through smarty in the default templates *} If you trust all admins and do not allow frontend users t...

After setting it to PHP 5.6 (which you should do until you're on 2.x) make sure to clear the cache. If you can't get into the admin before upgrades, clear it manually - empty everything from the folders /tmp/templates_c and /tmp/cache Also check your PHP error log, there'll be some clues in there wh...

They wouldn't be files, they would be templates within Design Manager. Look for any Products related templates that are marked as default, and try putting something at the top so you can see it in the frontend. Once you figure out which template you're using, you can start to make changes.

Sounds like something didn't go right during the upgrade, but yes that's probably the fix.

There is no procedure to upgrade it, it's been deprecated. It still works for now, but at some point you will want to switch to Navigator.