Blog Section

I'm proud to announce the first public release of the PYGUICMS project. Checkout the page http://dvm.zapto.org:8080/pyguicms-trac/wiki/PyguicmsDownload.

This release, like mentioned, is the first beta version that is publicly downloadable.

I have set all article types, links types (tags) in lower case. Like the system is case sensitive. A like like /links/list_by_category/?type=awk and /links/list_by_category/?type=AWK are both different! This said, it may break some indexed search engines.

Ticket 59 - If a comment is added and is not (x)html compliant, the page can't be displayed has been fixed. With the consequence that we can't add html code anymore for these different comments on articles, news, ... items.

This remove any link if you still use some <a> tag. This avoid to break and get an error on the page.

I got still some stupid spammers, but no breakage anymore. And like i get a mail when someone add a comment, i can quick remove these weird comments. All suspicious links are added to the banned words/urls. So, you are warned!

Ticket 55 - When a comment has been added, mail to the admin has been fixed. So my spambox get informed when someone add a comment, even when someone sign that unknow guestbook.

I don't know yet how i will fix ticket 59 - When a comment has been added, mail to the admin. I think that i first will work on a captcha system (ticket 9) before trying to fix ticket 59.

I got a first spammer who spammed the guicms replaced by pyguicms news item. This spammer used an invalid (x)html markup and that broke the page. The consequence was that the news item guicms replaced by pyguicms couldn't be displayed anymore. I created a ticket for this.

I also have a ticket: When a comment has been added, mail to the admin where i plan to work on it soon.

It's already more as a year now that i use trac. I'm very happy that i have done this step. trac is a tool to use when working on mid up to large scaled projects. Before using trac, i tried to remember all the bugs and features that i may need to work on. Many times i forget partially some things to fix, if i didn't forget it at all.

Now, when there's a "problem", i create a ticket. Specifying a release when i want that this ticket should be fixed. I can easy keep a view about "problems" that are still open. Even PYGUICMS users can create a ticket without the need to create a user account. Hopefully this will improve the whole project.

There's even a wiki system included in the trac. All documentation are made on the wiki of the trac. So that users can help to improve the poor PYGUICMS documentation. The documentation on the wiki can help to create the documentation that will be provided with the PYGUICMS sources.

trac can also show the source code of the project. Somethings like the websvn is included in it. With this, you can easy browse the sources and look to some parts of code without the need to checkout the reposition.

trac can do much more, it's even easy to extend it. There are already many plugings created by volunteers. I just wanted to resume a bit what has helped me much.

• pyguicms-trac - http://dvm.zapto.org:8080
• trac - http://trac.edgewall.org/

The GUICMS been redirect to PYGUCMS like noted in the news item. I hope this won't give to much troubles for users. The data of the GUICMS is already some time not updated anymore and there are no many reasons to go back to the old data. The old data has been keep as source and many pages are corrected and some more informations are added.

Google search result should be ignored, that's somethings bad. I hope that Google will index quickly all the PYGUICMS content from now. That why i have setup a redirect, in the hope that Google will abort all further indexing of all GUICMS stuff.

The project is now online and used in a test environment. I plan to continue to work on the code and at the same time on the data of the different sections like the articles, links, feed the blog and such. The development on the code will slow down a bit now. Working both, on code, and on the data may take much more time now. With using this tool, we may easier discover the bugs and the features that is still missing. I hope so to improve better my tool.

At this stage, i already need to add some more new tables into the database. One for banner images, one for pictures and another one to contain some different data files. The pictures table may contain some images so that we can include it in articles and such. For the files table, this should be contain different types of files. Configuration files, text files, binary files and for whatever goal. That will be useful in articles too.