Nailblog 2.0.2
2010-03-25 12:53 by Nailbar
Full installation: [nailblog-2.0.2.tar.gz]
2.0.1 to 2.0.2 patch: [nailblog-2.0.2-patch.tar.gz]
Added the file manager module. It's still a bit buggy but usable if you avoid experimenting too much.
Copying or moving a folder to another folder were a folder with the same name already exists is known to corrupt the index a bit.
Changelog:
- Added a file manager module.
- Renamed index.php to nailblog.php so it can be installed next to an existing system.
- Added nailblog_delete for removing files by GLOB.
- Added translations to Nailblog core and fixed translation related bug.
- Added anti-bot measurements to the blog module.
- Clicking blog entry titles switches between single entry and multi-entry view.
Bonus; installing several Nailblogs along with another site
All the Nailblog2 files are located inside the nailblog folder. The init file is from now on nailblog.php so, if you have a website already, and don't want to replace it with Nailblog, but install Nailblog alongside it, you just have to make sure that you have no folder named nailblog and no file named nailblog.php that will be overwritten.
If you want Nailblog to be your primary system then rename nailblog.php to index.php.
You can also install several different Nailblogs using the same core code. Just copy and rename the nailblog.php file and define different data folders for each copy.
Example:
index.php - the primary site (in this case something non-nailblog)
nailblog/ - the nailblog folder where all the nailblog code exists
nailblog.php - one Nailblog installation:
* $nailblog_data="../data1/";
test.php - another Nailblog installation:
* $nailblog_data="../data_test/";
In this example you get the old non-nailblog page when you visit the directory or index.php. By going to nailblog.php you access one Nailblog installation, and going to test.php you visit another.
Applying an upgrade patch you will automatically upgrade both Nailblog installations because they use the same code.
[Add comment]