CMS Made Simple Forums

.

No response from anyone yet. Are some of these things on any of the roadmaps?

To the best of my understanding these requests are so large that they likely will not happen soon. A few of them would also cause more issues than it would help and it could break backwards compatibility (which no one wants).

I know they did some work on the Print button, but I have no idea what was done.

Those seemed like very important things to have, so I will see how I can help (might take a long time though). But just hearing that those are good suggestions warms my heart.

Oh, I need to explain myself. In no way I wanted this to be a major undertaking, and in no way I want to clone another CMS. I always envisioned ingenious solutions to all of those requests:

1) Backup - there are modules for this, but they are not easy, give errors, not automatic, etc, etc. So a little consolidation and cleanup and the solution is available (from what I saw there are both sql and file backup modules available).

2) Undo - same here, not AJAX undo button, but just save previous versions of pages in a differential format (there is a module that saves whole pages).

3) Simult editing - I did not mean two people editing same page. I meant admin could attempt to edit same page in two windows, or have a page editor opened, and an editor changing the same page, template, etc. Just a warning that this page is being edited elsewhere is all I thought about.

4) Print button - same with News module, I really don't like what it produces on Google. Just awful and non-CMSMS-like  . BTW, was that News module issue solved?

replytomk3 wrote: 1) Backup - there are modules for this, but they are not easy, give errors, not automatic, etc, etc. So a little consolidation and cleanup and the solution is available (from what I saw there are both sql and file backup modules available).

There were modules at one point in time but with changes to the system they were never updated.

2) Undo - same here, not AJAX undo button, but just save previous versions of pages in a differential format (there is a module that saves whole pages).

This is not as easy as it sounds and versioning has been requested before. This is one of those features that has been determined as nice to have but difficult to implement. Currently there are other features and issues that have been deemed to be more important. I know for a fact though that if someone were to sponsor this feature, it wouldn't be turned down.

3) Simult editing - I did not mean two people editing same page. I meant admin could attempt to edit same page in two windows, or have a page editor opened, and an editor changing the same page, template, etc. Just a warning that this page is being edited elsewhere is all I thought about.

I originally thought this would require versioning and merging. A notification feature wouldn't be so bad. If you could please file a feature request for this. I am not a developer but it may just mean tagging a page and when you open the page with the tag existing it will display a message. We will also have to determine what period of time the tag would exist in the event you closed your browser without hitting submit. Otherwise the notification would come up if you closed your browser before submitting the page and if you did not really have the page open at that time.

4) Print button - same with News module, I really don't like what it produces on Google. Just awful and non-CMSMS-like  . BTW, was that News module issue solved?

This really isn't a google issue. This is just a matter of developing Pretty URLs for those modules.


All of the above items are very possible, however other tasks take a higher priority. What one person thinks as important probably isn't important to the majority of the community. If one person really needs a feature (including the above) sponsoring those projects is recommended. Obviously paid work will take a higher priority than donated time.

tyman00, very fair responses.

Hello,

I'm just chatting here.

Thank you for my dear 25382. You make me more convinced that *versioning* is a key on the path to undo, simultaneous editing, notification, conflicting changes resolution, review, approval, workflow and more. I speculate it is only a "version" attribute away from current code.

About "print button" : I think it insane to mess my content with such browser feature.

Have fun with CMSms

Pierre

Depending on the server, if you have access - you could use a cron job with tar and mysqldump to backup the website/database?

I can, but not a beginner user who will then cry help on the forum that their data has been lost. For that matter, I can do all of the above manually or semi-automated. But it does not mean I should.

replytomk3  watch for this to come out in a month or so... http://dev.cmsmadesimple.org/projects/siteutlities

I'm working hard on it and it will do some of the things you’re asking for... mostly the Backup which, with a little more work should lead to an "undo/restore" feature thou limited in the first phase... you can test the SVN... but I'm only 30% of my road map for phase one and have much more to do...

Cheers
Jeremy

Jeremy, will await your solution eagerly!

I am not sitting idle in the meantime. I am adding to my site every single day, slowly progressing towards my goals. As soon as I am able to, I will try to contribute in ways that I can.

Hello, so I made tons of movement on the DB side of things... you may now backup databases... I'm working on the cronjob script as well as the test scripts... but you can add all the profiles you want to and back them all up... not auto yet but it works and you can pull from the SVN anytime... but don't report bugs yet... and please don't use on a production unless you have tested it yourself and just want to take the risk... it's only beta and buck stops at you... Thought I'd share...

Cheers
Jeremy

Any time a mention of version history or page rollback comes up I have to chime in and say that this is single most important feature CMSMS lacks. Right now if a user screws up the content of a page it has to be recreated by hand or a database backup needs to be restored.

@Deak : I agree, hence my mantra : versioning, 25382, versioning, 25382, versioning, 25382, versioning, 25382...