LampCMS open source XSLT based content management
The first open source CMS that uses browser based XSLT transformation
Thu, 10 Sep 2009 19:08:31 -0500
Install wpd2html and odftools and openoffice and try to convert documents
0
Sat, 15 Aug 2009 20:45:46 -0500
Just have to finish up 2 forms: image signature and smart resize scripts and then can release the first package with some type of minimal installer that would at least create a first admin account
1
Fri, 14 Aug 2009 19:17:55 -0500
Now the xsl transformation takes place on the server for not logged-in users and on the browser for logged-in users. A fail-safe check has also been added to test that user's browser is capable
of xsl transformation. This is done by sending a special cookie from the javascript. This javascript is only added to the transformed HTML document when XSL transformation is done on the browser.
So if the user receives this cookie it means the browser was able to transform the XML document correctly.
The reason for this is to be absolutely sure that search engine bots will receive HTML version of the pages.
In the past the XSL transformation was done on the browser if the browser supplied a valid site cookie. The logic behind it was that search bots don't accept cookies, therefore it was safe to assume that if cookie is present, then we are dealing with a regular browser and therefore can send a page in XML format and have the browser perform the transformation. The experience has shown that while it worked really well for Yahoo search engine, the Google has not picked up most of our pages yet.
We'll see what will happend now.
The reason for this is to be absolutely sure that search engine bots will receive HTML version of the pages.
In the past the XSL transformation was done on the browser if the browser supplied a valid site cookie. The logic behind it was that search bots don't accept cookies, therefore it was safe to assume that if cookie is present, then we are dealing with a regular browser and therefore can send a page in XML format and have the browser perform the transformation. The experience has shown that while it worked really well for Yahoo search engine, the Google has not picked up most of our pages yet.
We'll see what will happend now.
0
Thu, 10 Sep 2009 19:09:38 -0500
Things that have to be done/fixed ASAP:
Editing of existing post by blog owner
Deleting of post (
when post is deleted, it affects the next post because next post's prev_thred_id
is now points to deleted post... Also BLOG_INFO table has to be updated - it has total_posts
per blog, last_post_timestamp, latest_post_id, which may also need to be updated. Lastly,
the .rss file may have to be deleted in the deleted posts in among the latest 25 posts)
Also deleting of post show not really delete it, just mark it as deleted in a MESSAGES table, so it may be 'undeleted'
Editing of existing post - just present the same page as addblogpost only the RTE will have the existing post in it. User will be able to change body, title, weight, type, and date of 'when to show' and 'expiration' date.
onPostEdit even should be fired using fileEvent dispatcher because .rss file may have to be updated.
The deleting of post, closing it for new comments may also be done from the personal page (with list of posts) by using small buttons that will trigger some ajax based prompts. This will require the use of security tokens to avoid XSS hacks.
Editing of existing post by blog owner
Deleting of post (
when post is deleted, it affects the next post because next post's prev_thred_id
is now points to deleted post... Also BLOG_INFO table has to be updated - it has total_posts
per blog, last_post_timestamp, latest_post_id, which may also need to be updated. Lastly,
the .rss file may have to be deleted in the deleted posts in among the latest 25 posts)
Also deleting of post show not really delete it, just mark it as deleted in a MESSAGES table, so it may be 'undeleted'
Editing of existing post - just present the same page as addblogpost only the RTE will have the existing post in it. User will be able to change body, title, weight, type, and date of 'when to show' and 'expiration' date.
onPostEdit even should be fired using fileEvent dispatcher because .rss file may have to be updated.
The deleting of post, closing it for new comments may also be done from the personal page (with list of posts) by using small buttons that will trigger some ajax based prompts. This will require the use of security tokens to avoid XSS hacks.
0
