Hi!
We may consider to remove support for #CMSimple hide# and #CMSimple remove#. The same functionality is already available via page_params, but page_params has the advantage that plugins can actually check whether a page is hidden or removed (aka. unpublished) by looking at the page data. This distinction not possible with the respective CMSimple scripting, even though it is sometimes necessary, see, for instance, http://cmsimpleforum.com/viewtopic.php? ... =10#p55612.
If we don't want to remove support for these two CMSimple scripts for backward compatibility reasons, we should consider to integrate page_params into the core (what appears to be reasonable, anyway), and to let the core set the respective page data if a page is hidden or removed via scripting.
Either way, we should consider to introduce a counterpart to hide(), so plugins can easily check whether a page is removed without having to use the $pd_router.
Remove support for #CMSimple hide|remove#
Remove support for #CMSimple hide|remove#
Christoph M. Becker – Plugins for CMSimple_XH
Re: Remove support for #CMSimple hide|remove#
Now – considering the issue – I see thing like this:
1. Pages can be:
a. Fully accessible
b. Accessible with restriction – by time, within a time span, controlled by a plugin (Register_XH, Memberspages, an future plugin with similar functionality)
c. Hidden from navigation – used by plugins, newsboxes etc.
d. Removed from content, but still accessible to the admin – e.g. for future use, as notes, warnings, hints, ToDos).
2. If any page manager shall become a standard tool for pages creation, it shall have the features 1.a-d included (evtl. synchronized with editor outputs). So the admin maz set all details in one place – instead of setting them on more various places.
E.g.[ external image ]
1. Pages can be:
a. Fully accessible
b. Accessible with restriction – by time, within a time span, controlled by a plugin (Register_XH, Memberspages, an future plugin with similar functionality)
c. Hidden from navigation – used by plugins, newsboxes etc.
d. Removed from content, but still accessible to the admin – e.g. for future use, as notes, warnings, hints, ToDos).
2. If any page manager shall become a standard tool for pages creation, it shall have the features 1.a-d included (evtl. synchronized with editor outputs). So the admin maz set all details in one place – instead of setting them on more various places.
E.g.[ external image ]
CMSimple.sk
It's no shame to ask for an answer if all efforts failed.
But it's awful to ask without any effort to find the answer yourself.
It's no shame to ask for an answer if all efforts failed.
But it's awful to ask without any effort to find the answer yourself.