Geneone 0.4.6 Upgrade
November 21st, 2005
I just upgraded the version of Geneone here to version 0.4.6 - the latest build.
Theres some visible changes such as the improved community portal, change e-mail address and FOAF profile import. I have also added support for the hAtom microformat. Since I haven’t found any software which supports hAtom yet, I’m not 100% sure it’s valid but if anyone comes across a hAtom parser, let me know.
Administrators can now edit users profiles and users can be stopped from editing their profile through a permission. Table naming has also been cleaned up (for example we used to have gene_objectrevisions and gene_object_taxonomy. I have also updated the PEAR.php file and added the Incutio XML-RPC library.
Objects can now have additional properties and settings. Pinging of web services such as Technorati has been implemented through a property. Blog objects are eventually going to have a configuration page where properties such as services to ping will be configured. The object system allows there to be more than one blog, each of which will have different settings.
- Uncategorized
- Comments(5)
Digg
StumbleUpon
Should I try this out for my blog?
WordPress crashed my server, so now I’m stuck.
It’s still alpha software and unsupported so I wouldn’t recommend using it unless you know PHP well or you’d like to try out what the software can do. You can get version 0.4.3 at http://cow.neondragon.net/index.php/245-Geneone-043-Technology-Preview-Released; I’m trying to get 0.4.6 online but I’m having some problems uploading it to the server at the moment (SVN).
Is there any possibility for an anonymous SVN account with read only access?
It’s possible but I don’t currently have the Geneone code stored in SVN - the htdocs folder for this site is in SVN and is what I use to update the website. It contains a few extra things such as configurations, themes and passwords so I won’t open that up.
I’ll see if I can convince neonDragon to allow us to have an additional separate HTTP repo for Geneone source.
If I currently doesn’t remember wrong about the security of SVN.
All you need to do is to create a new branch in your SVN repository where you haven’t included your passwords etc..
Edit:
Additionally you could just have a renamed copy of you’re configuration files in your working copy, but of course that is a little more work.
I had (it is currently down) many repositories on my computer, one for each project, where some had many branches where different released version where stored.
Makes it easier to downgrade then to remember the revision number for a release.
In addition I had one common repository with no trunk folder, but only branches, where configuration files where stored.
The trick is to not include your configuration files in your trunk folder and create a batch script that checkout first your normal repository and then the configuration repository-branch which matches the project.
It is a little more work, but makes it very easy to administrate releases and anonymous access for projects where configurations with passwords and similar entry’s are used.