1.1.0 beta2 fixes the paths and escaping bugs spotted by Jerome, and adds a couple of new features:
-
comments are now enabled for pages (called static posts in LP)
-
the new
NestedPagesplugin sorts and displays nested pages in the sidebar
The two above features will hopefully enable us to manage documentation and support requests without having to resort to a Wiki. As usual, the ChangeLog is available on SourceForge, and also copied below.
2005-07-11 17:32 ludo * classes/Frontend.php, VERSION.txt: bump version number 2005-07-11 17:31 ludo * templates/: elastic_minimal/en_US.UTF-8/static.xml, elastic_minimal/it_IT.UTF-8/sidebar.xml, elastic_minimal/it_IT.UTF-8/static.xml, kubrick/en_US.ISO-8859-1/sidebar.xml, kubrick/en_US.ISO-8859-1/static.xml, kubrick/en_US.UTF-8/sidebar.xml, kubrick/en_US.UTF-8/static.xml: add nested_pages to sidebar and comments to pages 2005-07-11 17:25 ludo * templates/elastic_minimal/en_US.UTF-8/sidebar.xml: add nested_pages plugin 2005-07-11 16:41 ludo * plugins/NestedPages.php: added TODO: for skip_inactive_branches 2005-07-11 16:39 ludo * plugins/NestedPages.php: added TODO 2005-07-11 16:37 ludo * plugins/NestedPages.php: output the title for childless pages only if there are any 2005-07-11 16:21 ludo * wp-compat.php: should not be needed anymore 2005-07-11 15:14 ludo * plugins/NestedPages.php: seems to work 2005-07-10 15:35 ludo * wp-plugin/LightPressModRewrite.php: fix archives sitemap rule add search rules 2005-07-09 17:31 ludo * templates/elastic_minimal/en_US.UTF-8/static.xml: hide comments header if there are no comments and comments are disabled 2005-07-09 17:29 ludo * plugins/AdminOptions.php: enable for posts and pages 2005-07-09 17:27 ludo * plugins/CommentSpam.php: set default_context as int 2005-07-09 17:26 ludo * plugins/PostComment.php: grrrrrrr set default_context as int 2005-07-09 17:24 ludo * plugins/: CommentSpam.php, PostComment.php: enable for posts and pages 2005-07-09 17:23 ludo * templates/elastic_minimal/en_US.UTF-8/static.xml: add comments template variables 2005-07-09 17:23 ludo * classes/PostGenericAction.php: enable for contexts other than 'post' 2005-07-09 17:15 ludo * wp-plugin/main.php: add a few 'dirname's to detect correct .htaccess location, it's ugly but it works 2005-07-09 17:12 ludo * wp-plugin/LightPressOptions.php: use install_type attribute instead of a method as it's only used once 2005-07-09 17:11 ludo * wp-plugin/options.php: use saved lp_opt_install_type to decide if we have to update .htaccess otherwise we get an error on first install (install_type is root but no options are set yet) 2005-07-09 09:20 darkcanuck * wp-plugin/: LightPressOptions.php, options.php: Moved version check to options class, removed check/error code from options page (no need to check for Frontend since was already done by class) 2005-07-09 05:54 darkcanuck * wp-plugin/: LightPressOptions.php, options.php: Refactoring of options code, re-activated LP->WP options sync for root mode and deleted obsolete fork-releted code 2005-07-09 03:16 darkcanuck * wp-plugin/LightPressOptions.php: Fixed escaping bug(s) due to WP's irrational need to escape *everything* 2005-07-09 01:49 darkcanuck * lightpress.php: Updated plugin version & instructions
ludo, I would never install a PHP application for which there was no support forum or wiki — unless it was so basic that no mods would ever be required. In order to try and understand the basic structure of a WordPress template, I prepared a diagram. I uploaded it to an image hosting service. you can see it at:
http://tinypic.com/71gwua
I'd like to see something similar for LightPress. It could simply be <PRE> text. Another thing: I would not want to download a zip archive just to see what's in the README file. Could you post the README file here… or is the ChangeLog the only documentation available?
Kerim, we already have a support forum on Textdrive, and will be getting a Trac instance etc. soon courtesy of Textdrive.
In the meantime, we will start writing a few much needed docs and references, publishing them here and opening comments. As long as things are easily reachable and readers can discuss the docs, I don't think there's much difference in adding a wiki, at least in this initial stage.
Your diagram looks good, if you feel like helping us you are more than welcome. :)
Oh, there's no README file. We have an INSTALL file which is identical to the link you find on the sidebar, where there's also an About doc that should answer your basic questions.
I like the diagram, we should definitely do something like that.
Ludo, are you updating this site to beta2 soon?
It's already running beta2, apart from the version number. :)
My apologies. I didn't notice the sidebar link to the support forum before. If I need to ask more questions in future I will use the forum. I did read the draft INSTALL document. At the moment it's somewhat technical and brief. Thank you for your comments about the diagram. The first post in the forum said you were in desperate need of a logo. I realize logos are a matter of personal taste, but my thought was that a lightweight sans-serif font would be suitable. I have been experimenting with a "kubrick" replacement header, so I added a Lightpress logo using the Monotype font. You can see it here (6574 bytes):
http://tinypic.com/71lnbl
If you like it, you are welcome to use it. I am more of a graphic designer than coder. I still haven't configured MySQL correctly on my Windows XP machine, for example. I would be very happy to prepare diagrams and screenshots, but the difficulty is that I wouldn't want to have to reverse engineer the source code to figure out what to put into diagrams. Screenshots are easier. It would be nice to have some screenshots of the install process when everything is stable. I made a composite picture of the WordPress screenshots:
http://tinypic.com/71lnw1