XMLRPC updated to the latest version because of the vulnerabilities.
Netdoc look and feel updated in 1.62. More eye candy... ;-)

I'm very happy to announce that Netdoc 1.6 has a full Firefox support. It also turned out very well – I was surprised to see how good Firefox actually is, for a developer, and overall. The wysiwyg editor is now a tad better with Firefox than it is with Internet Explorer, since FF is just a tad better browser than IE. I personally changed my default editor as Firefox, as it seems that there are very few reasons not to change.
Next, Safari...?
New project type: filearea, for archiving files or providing a download area.
One use case that has been very succesful at PC Users of Finland organization, is to create documents collaboratively on the site, then archive them as encrypted PDFs, which Netdoc is able to generate automatically.
Netdoc 1.510 employs our SlashdotProof technology to prevent sites running on Netdoc suffering from the Slashdot effect. And generally the server should be able to handle the load more effectively.
If there are large files being downloaded, that may still affect adversely for the overall performance.
One milestone reached again!
Again, there are a lot of improvements, mainly in the editor this time. One of the biggest features is the slide show project type.
Many small but important improvements. To smooth out the corners.
Help System streamlined - help can have comments like the rest of the site.
Thanks to Noah Mapstead for help.
Quite a few changes "inside the hood".
1.4 is quite a huge update.
Aside from the thousands of minor improvements and fixes, a couple of more bigger features are in this release:
First, there are the user privileges, which should be finalized in this release.
Then, perhaps even a bigger update, is that files and pictures can be saved into the database. This has a few implications:
Some people may want to store even all the pictures into the database - if you want a real easy site management. There will be a quite a minor performance penalty if all the pictures are stored into the database.
The setting that affects how files are handled is in Project Properties/Cache.
For the last week or so there has been many little fixes. Netdoc has been tested on different setups and mostly the installing procedure is straight-lined.
For example, the installer will now check for correct file permissions and for mod_rewrite.
If there are any problems in installing Netdoc, please let us know.
Netdoc has switched from Turck MMCache to eAccelerator.
Turck MMCache is a great product but unfortunately it is not maintained anymore. However, there is a group of motivated developers now behind the successor of Turck MMCache, and the project is called eAccelerator. Netdoc requires eAccelerator, and eA is included in the Netdoc package as well.
Linux users have to compile eA themselves, for Windows users there are eAccelerator binaries.
Here it is, the version 1.0 of Netdoc!
Please pay the license fee and make Netdoc possible in the future as well.
In the next minor release we will see a WYSIWYG editor for Mozilla.
All the known bugs have now been fixed, which there were some in the release candidates. If you have Netdoc installed, you can update it from the shell.
> cd netdoc
> php admin/update.php
This way you can update your installation of Netdoc in the shell with the update.php script. Updating a server based software can't be much easier than that, can it?
(And don't forget to pay for the license fee.)
New updates:
Frontend editing is now better -- you can actually use it to publish blog posts, instead of just editing them or editing web pages.
Granted, this comes a little late.
Use Admin->Update. People who download and install the .zip should do Admin->Update as their first task to see if there are new updates.
Ctrl-S works now in Frontend editing. And just in case, F2 does the same task as Ctrl-S. It seems that Firefox users need to use F2, because Ctrl-S pops up a "Save webpage as" dialog.
Of course, I'm talking about saving. No more lost content.
Some bugs fixed in topic saving - those new saving features introduced a couple of bugs of course.
Netdoc approaches 1.0 version! Everything seems good, things are clicking.
Quite a few changes.
Some UI changes:
A couple of fixes in
A change in the editor:
Also one small fix.
Something useful:
IIS (Internet Information Services, Microsoft's web server) compatibility.
Tested with IIS 6.0, ISAPI and fastcgi modes and ISAPI_Rewrite.
Statistics:
Accessible from the menu (Project -> Statistics).
Redirects:
More cache features:
Netdoc's RSS feeds normally contain 20 newest blog posts. A common practice on the web nowadays is to return the whole feed if any of the posts have been changed (since the last time an rss aggregator, for example Bloglines, requested the feed) or give HTTP 304 Not Modified if the feed is up to date (to that RSS aggregator).
Netdoc tries to go one step further: if an RSS feed reader requests the feed with the If-None-Match or If-Modified-Since header, Netdoc will return only the blog posts that have been modified after that timestamp.
This is to say that ETags are now timestamps and only the changed posts can be returned to the RSS aggregator, which should save bandwidth for large blogging hosts.
This idea came to my mind when reading this post.
Caching is fixed a bit.
Existing ND users: go to shell and issue a command php admin/update.php to update your NDs.
Usually the frontend editing feature (the little ND box on websites) appears when the user has logged into ND and clicked the remember me checkbox. Then, a cookie is placed on the user's computer, and that user is remembered and can use the little ND box.
Something new to this scheme: a website can now have a login box, which the users can use to log in or out, and can have the little ND box in use on a session basis. This way the little ND box can be used from a shared machine.
So, this feature is for larger groups, schools, communitites etc, who want to have a blog for each member or a shared blog for some member.
Finally a big update. 1.00 Release Candidate 2 includes, among others:
Still another bug fixed.
When creating a new project of type Website the frontend editing feature couldn't be accessed because there were some old versions of files in the zip package. (I'm talking about the little ND menu at the top left corner.)