CMS Made Simple Forums

I think you're forgetting the core audience here.  People with shared accounts that barely have access to anything.

Neat idea, but probably beyond the scope of the core functions.  Most people don't need to send out batches of emails.  If they do, then we come up with a specialized way to set that up outside of the core system.

I think wasn't clear.
I was just meaning that one solution should not exclude the other.
In particular when you have the scheduler execute at each page access, is very simple to setup a similar script that execute the scheduler on cron base. Only the modality that execute such script is changing.

About having code running in parallel (threading) it is not possible in php.
Looking around in the web I found the following function that should work both for unix and windows.
It runs at command line something but basically redirect the output to /dev/null (for unix) so the exec() function does not wait for the end of the execution.

/dev/null &"); 
      }
  }
}
?>
This would solve loading time if the scheduler is called at each webpage hit.
The drawback is that such solution still need php-cgi installed.

What I've in mind is purely on useability side. CMSMS is great in features, but what I miss is straightforwardness on the most important things regular user wise: afaik the admin side looks pretty much the same for content creator. So I think what would be great that when a content creating user (and why not anyone else) gets into the admin panel s/he could get a direct possibility to write articles. So the content module could be the most important and featured module in the admin panel frontpage. This would greatly make things more straigtforward for those non-techy regular users who just want to add new content and edit existing content directly when they get in (as they don't care about anything else).

I also miss paragraph tags around the generated content, I dislike all linechanges being BR-tags.

Other than that I don't have anything to complain about and CMSMS is a great piece of software; pretty close to how I'd have done things if I had the time

Merri wrote: I dislike all linechanges being BR-tags.

Try to use TinyMCE  - it's faster and all line breaks are paragraphs ...

Do you an approximate release date for v2.0?

Was shooting for June, but given the fact that I'm so overloaded with my dayjob that I can see it slipping very quickly.

A little off-topic, but since 2.0 is going to be released sometimes around June, what is the release date for 1.1 then? Sorry, but I couldn't find it.

There won't be a 1.1.  We're going right to 2.0 because of the large amount of changes.

Found something useful that can be integrated as module in future release
http://codepress.fermads.net/
This is a javascript code editor with syntax highlighting and code competition.
It can be useful in editing css and template.

I am not very deep in cms code but I guess that such support need some code in the core, like for wysiwyg editor and then in the modules that edit "code".

I would like to ask for a method whereby someone with editing permission for pages has to submit new or updated content to a reviewer before it is published / made public.

Is that a possibility for v2?

@Anastasis

There exists a patch for that 

http://dev.cmsmadesimple.org/tracker/in ... 6&atid=103

I'm jumping in late on this thread, but I'd like to add my two cents anyway. I'd really love to see front end user permissions built into the core of the CMS.

Let me tell you my pain now so you see why I'm asking. I recently a site for the dojo where I take karate. The site offers password protected pages to students in each of the different ranks (white, yellow, etc. belts). Using the FEU/CustomContent modules, I've created a separate group for each. To maintain separate sets of pages for each rank, I have to create a separate template for each rank. So, I have a SecurePages-WhiteBelt template, a SecurePages-YellowBelt template, etc. If I make any change to the look of the site, I have to update about ten different templates with the same change. And getting all the smarty {if customcontent_memberof_group} tags correct was a real pain! Worse, I had to communicate all of this to the school's owner, who isn't at all computer savvy. Her eyes just glazed over when I started describing how to add a new page to her site.

It would be soooooooo much better if there were another tab in the content editing screens for permissions. The tab should have little checkboxes for which FEU groups should have access to the page. One template for the site. Just check the boxes to secure the page.

By integrating front end security into the core, modules could particpate, too. I could set up a gallery that was off limits to general surfers but available to logged in users. Same for news pages, search results, etc., etc.

If I were smart enough, I'd hack the core to do this myself. But, if I could do that I'd probably write my own CMS from the get-go.

Thanks for listening,
Tim

Separate topic, separate note: On the PHP5 topic, I host some sites with a company that uses the HSphere control panel system. HSphere, made by PSoft, does not support PHP5. Therefore, even though this hosting company really wants to upgrade to PHP5, they can't until PSoft gets its act together. PSoft has been promising an upgrade to HSphere for a couple of years now and has delivered nothing but buggy alpha-quality code.

You can't always get down on the hosting company for not offering the latest and greatest. Often times they are looking out for our best interests. But, their hands are tied by the platform choices they make, just like we get tied up in the technology choices we make.

I'll have to look for another host to use CMSMS 2 because of the PHP5 requirement. Since my current host has been so good, this is not something I'm looking forward to nor is it something I will do without a lot of hesitation. I've been burned badly by very unprofessional hosting companies in the past.

Tim

@Anastasis:
This will be in the core of CMSMS 2.0, though probably as an option that needs to be flipped on.  With the versioning stuff that will be built in, the workflow system will make a nice extension.

@skypanther:
Yup, I agree. I've gone back and forth on this topic, but convinced myself that frontend permissions needs to be in 2.0.  It will be a basic ACL system and only have the basics of login/logout functionality...  but it'll be there.  I'm going to probably start fleshing out the details (read: coding) in the next couple of weeks.

Also, I know the php5 thing is a touchy subject.  It's a shame that we really have to have this period of time where hosts can't/won't upgrade to the new stuff.  I know where they're coming from...  there is a ton of code out there that isn't going to play nice with php5 and they're afraid of the tons of support calls they're going to get.  We're seriously taking a risk by doing the php5-only thing here, but it's a natural progression that NEEDS to be done.  Eventually all of the systems are going to do it, we just happen to be on the front of the curve.  The benefits just outweigh all else at this point...

Thanks Cyberman and Ted for your replies.