phpns

2.2.4 released

Posted by alecwh on Tuesday October 20, 2009 6:14 pm

Phpns 2.2.4 fixes many issues with previous versions, as well as improves the entire user interface with a new theme!

• Ended "patch" nonsense. (All future version will be actual versions...)
• New default theme, UI enhancements
• Removed codepress as template editor (no longer maintained, broken)
• Fixed IE, Safari, Firefox 3.5+ article saving bug (button grays out)
• Fixed other bugs dealing with https://
• Fixed various typos
• Fixed other minor issues
• Updated docs with new development info

You can download it here. A patch can be found here. To install the patch, upgrade to at least 2.2.3 and overwrite all files. The screenshots page has been updated with new images.

Thanks for your support! If you want to donate to the project, click here.

Glad to see this project alive and kicking! Going to try the new version now.

Goodluck to you and the community working on keeping development alive. This certainly beats the Hell out of Cutenews and FanUpdate (both dead but still in use for some reason).

A quick note, the footer for phpns still says it's version 2.2.3 patch 2

Annika: Not for me. Can you verify that you have indeed upgraded your installation? And even better, can you open up a new Bitbucket issue? (It requires no registration, just a report.)

http://bitbucket.org/alecwh/phpns/issues/new/

I'm sorry about the bug scare. It so happened that the footer was incorrect only during install. When using the actual script, the footer is up to date.

I find bug ! Upload folder dont exist in 2.2.4 !

efs: Yes, I'll try and have that fixed in the next release. It was a problem that emerged from our switch from Bazaar to Mercurial. If you wouldn't mind, please file a bug report.

When I try to upload images I get this message - The image upload returned an error, which means the file was not an image, or we had trouble moving the file to (images/uploads). Check the permissions for the directory.

I changed the permission on the phpns/images folder to 777 and it didn't resolve the problem. My image was a .jpg file. I'm getting by using ftp of the images to my site and then using a url to incorporate in my article. Maybe this is the same problem that efs is reporting.

Name (required)
Email (not published) (required)
Website

What is 56 plus 2?