CMS Made Simple Forums

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).

There can only be one default {content} tag in the hierarchy of templates, it's where cmsms does all its cmsms-y things. The easiest option is to move it further down in the hierarchy (so it's not even in the parent template).

Unfortunately Amazon removed the functionality that we used to obtain those figures, and the current forge is such an old beast that nobody wants to take it on to figure out another method. It is planned functionality for the forge's replacement though.

I'm not sure that would be possible, or a good idea if it was. You'll likely just end up in some infinite loop.

It looks like you've done it correctly, is there any chance your DirectoryIndex isn't configured correctly, and/or you have an index.html or similar file in your site's directory?

Generally you wouldn't add PHP directly to your templates, as the power of CMSMS is in the Smarty templating engine - and most functions suitable for templates can be done in Smarty. If you do need PHP for specific functions, or when it's more efficient non-template logic, you can use User Define Ta...

Looks quite similar to this known issue: http://dev.cmsmadesimple.org/bug/view/12678

It's not really possible on the current forge, but it's very high on the wish list for the replacement (whatever form that ends up taking). I'd also love to see Module Manager check for it too.

In our most recent newsletter, we announced that we would be attempting to release updates on a scheduled date, starting with 2.2.20 on April 8, 2024 (today). While we do have a release candidate ready, we are still chasing down some issues with the phar installer on newer PHP versions. To this end,...

For the menumanager thing it might be a php version, I'm not sure. Once you get to 2.x you'll want to switch your menus to Navigator anyway. To change the admin theme you do it in My Preferences > My Account (nav might be slightly different in 1.x, I can't remember that far back).