ionize CMS forum

You will always come across directories needing to be writable, especially when there is functionality that allows image uploading, file uploading, image resizing.
Sure, it is possible for a script to CHMOD a directory or file back to a 'safe' level but with the variety of different server configurations, different implementations of Apache, that doesn't always work 100% of the time.

I see where you are going with the "get data from the DB and cache it" but realistically, the only real benfit you are going to get is if the webiste is under very heavy demand, otherwise reading/writing to disc is far less resource intensive (and quicker).

Sounds like some files where not uploaded correctly.

- Who are you ?
I'm John, a freelance web developer, though I seem to spend most of my time working on OpenSource projects.

- Which CMS were you using before Ionize, why was it horrible or better ?
Mostly I used RavenNuke but that's because until very recently, I was on the development team for a number of years. I still use it when it fits the clients requirements because it's a great system, easy to work with and develop for BUT since I left, the release cycle is just to long for it to be able to keep up with modern technologies like HTML 5.

- Why did you switch to Ionize ?
I haven't really 'switched' - I use whatever fits the clients (or my own) requirements. Ionize is simple to install, simple to use and most importantly, easy to use for novices. It is search engine friendly and has multi-lingual support. Ionize also uses the great Code Igniter framework.

- What things made you happy in Ionize ?
Multi-lingual support - it is not enough to have multi-lingual admin area's etc, a CMS has to be able to support multi-lingual content as well - Ionize does this extremely well and even has SEO optimization for that content as well.
It is easy to install, extremely easy to use and most importantly, it is intuitive to use - you don't need to spend any time getting familiar with it.

- How would you introduce the benefits of Ionize to your client ?
I would only recommend Ionize for very simple sites at the moment or very big sites that needs lots of functionality to take advantage of the CI Framework.

- About what were you disappointed or frustrated in Ionize ?
Lack of a contact form is extremely annoying! I know no one wants to add modules etc before Ionize v 1.0 BUT for people that cannot code (end users) it prevents them from using this great CMS because it doesn't have this one basic "must have" feature.
I believe quite strongly that any website must have certain basic functionality and a contact form is one of them.

The tinyMCE editor is pretty good, though personally I prefer CKeditor because it ensures any user inputted html used is xHTML compliant - I don't think tinyMCE enforces web standards.

Not entirely sure that would be of benefit since all versions up to and including 0.9.6 are bug fixes (with some enhancements, so anyone using anything below 0.9.6 should upgrade to 0.9.6
A few are using the latest (not yet publicly released) 0.9.7 so realistically, there is only a need for specific forums for those two versions, at least until 0.9.7 is 'officially' released as a stable "for production" environment.

Having said all that, what would be REALLY useful is if people could prefix the post subject line with the version;
[0.9.6] My subject here
just to help the moderators out.

I didn't actually see any upgrade script in the Github repository for the DB to go from 0.9.6 to 0.9.7 so I'd assume, at least for now, that 0.9.7 is for clean installs only. Of course it would be easy to write a little migration script if you wanted to by comparing the schema..

OK looks like this is a local issue.
I'm using Ubnutu Linux and FireFox 5.0 to replicate the issue above.

With Ubuntu Linux and Chrome 12.0.742.91 (87961) Ubuntu 11.04 the Upload button only half greys out when I hover my mouse over the button but the button IS clickable if I am very careful with the mouse pointer - so I can at least carry on uploading images now.

Not sure if this is a cross-browser compatibility issues with Mootools (which I hate) and or the CSS but I'll try and dive into it some more.

Sounds like a bug, you should edit your Subject line to indicate which version of Ionize you are using

I just noticed if you use the left hand directory tree menu and add an article there, I don't see any options for adding meta data for the article.
However, if you look at the header menu under Content-> Create Page..
or use the icon New Page (centre top of the dashboard) those allow you to set the meta data when you create the article.
I wonder why those options are missing when using the menu tree links, maybe a bug or just an oversight.

I had some initial trouble installing this.
The first error was because the admin side could not find the module directory; the zip package uses the directory name modules/tcontact but the code is actually looking for modules/Tcontact (according to the error message I got) so I renamed the directory and that worked ok.
The language file names were now incorrect so I renamed those as well.

This bit in the readme has me slightly confused;

I created the file myself because it wasn't in the package but "then register as an article" ? What is that all about?

I know I can just drop

<ion:tcontact >
 <ion:tcontactform>
 </ion:tcontactform>
 </ion:tcontact>

into another existing view page like MySpecialPage but I don't want to do that, I want the contact form to have it's own unique view page.

You can probably still edit it directly in;
applications/errors/error_404.php