CMS Made Simple Forums

The system checks for a minimum version of 5.7.44. It may work with 5.7.42 but if you run into issues you should probably have it upgraded. The recommended version is currently 8.3.0.

I haven't heard of the error page issue, if you can produce this reliably on a clean site (e.g. nothing special on the error page itself) then please file a bug report with steps to reproduce. For the Deprecated warnings, please see the release announcement for 2.2.20 (https://forum.cmsmadesimple.or...

See topic viewtopic.php?t=84040

The devs are looking into it, for now you may be able to work around it by using {content} directly rather than assigning it to a variable first.

I tested the form and it's fine, but FormBuilder sometimes gets false positives for the xss attempts. Feel free to DM me with the email address you'd like to use and I'll send you a Slack invite.

I just tested in 2.2.20 and it works, perhaps it was a core bug that's been fixed? Otherwise not sure, but be sure to check error logs and file a bug report if it's reproduceable.

Hello fans of CMS Made Simple! Today we are announcing the release of CMS Made Simple 2.2.20 - Saguenay, an incremental bug fix and stability release. This version addresses the much awaited support to the most recent versions of PHP, making it stable with PHP 8.3.0+. We have also tested thoroughly ...

You can likely ignore this, some of the checks need to be updated for things that have changed in newer php versions. It's on our to-do list.

The index.php shouldn't be edited. Like any other content management system, this file is for compiling your content with your templates. The simplicity comes in the separation of content from design - the content editor has a simple page editor, while the developer has a powerful templating system....

You're using the sample template, which is fine, but you'll need to edit it to your liking in Layout > Design Manager. If you're not comfortable editing html/css/Smarty, you may wish to consult with a web developer to get your site set up the way you like it, then you can manage the content via Cont...

You must use a unique block identifier for each block, and content_en is reserved for the default {content} block. So change the block=content_en parameter to something different for each ECB2 tag. Below is a small example code: {content_module module=ECB2 field=textinput block=content_en label='Sma...

Using a filepicker profile or the top parameter will cause the ECB2 tag to only store the path and filename relative to that profile or top directory. It assumes you know the path you defined in the tag, so you also use that path in your templates to display the file. e.g. if you use {content_module...

This is with ECB2 installed? I haven't run into that, but make sure you're adding all of the required parameters e.g. {content_module module=ECB2 field=file_picker block=test type=image} If you can recreate it then you should file a bug report on the module's forge page, Chris is usually pretty quic...

Ah, gotcha. I don't think that would be possible without creating your own admin template. You might want to look at ECB2 though, it has a file_picker field that includes a thumbnail, among many other options that greatly expand the default fields available.

I'm not entirely sure what you want, maybe a screenshot would help?

The thumbnail generation is in File Manager, not File Picker.

It does by default, but only if it has a thumbnail file (usually generated if uploaded via filepicker or file manager). If you uploaded it through your OS, for example, you'll need to trigger the generation one at a time in File Picker (I'm hoping for a bulk solution at some point).