Home » AWSOM News (Page 16)
Category Archives: AWSOM News
AWSOM Pixgallery 4.5.0 released
AWSOM Pixgallery 4.5.0 for WordPress has now been released and is available from it’s product page at AWSOM.org. This new version brings in many upgrades to the workflow model, now named the “FastFlow” system, which makes it easy and quick to get your images up and available for view. A guide is now available to help you understand how to get started with Pixgallery using this sytem. Additionally the much requested Individual Comment system is now in place, so you can get feedback on any gallery or image directly. Please let me know your thoughts on the new version and post any issues or questions on the support forums at Harknell.com.
AWSOM Pixgallery 4.5.0 Beta 2 now available for Download
The 2nd and final Beta for the new AWSOM Pixgallery 4.5.0 release is now available for download from the Pixgallery Product Page at AWSOM.org or by direct link here. This release is a near final release of version 4.5.0 and has the per image commenting system implemented as well as other new features and bug fixes. Please let me know if you encounter any issues or have feedback on any of the new features.
(And Updated One Last Time) Current Development Snapshot: AWSOM Pixgallery 4.5.0
In Production: AWSOM Pixgallery
Version: 4.5.0
Finished New Features:
1) Direct Links to Paginated Gallery Pages (think Google numbered links on search pages)
2) Edit/Add Gallery info link on page when logged into site
3) Image Caption System Fix (Captions are now unique for Images with the same name in different Galleries)
4) Better Workflow with return links when adding Captions from the web page (you can now click a link to return to the same page you left to add a caption to an Image or Gallery)
5) Sort Order by number added as new sort option for Galleries and Images (you can designate the order of Images and Galleries by assigning them order numbers)
6) Sub Galleries can now have individual Captions.
7) Preliminary fix for Windows IIS issues
8) updated: Now you can edit and delete from “View all Captions” and “View all Galleries” views, with speed workflow increases built in.
9) Per Image commenting Working! Now doing testing and cleanup/optimizing.
10) New Watermarking Option using .gif files
AWSOM Pixgallery 4.5.0 beta with IIS Test Fix code Released
Hi everyone, a beta of the AWSOM Pixgallery 4.5.0 plugin is now available for download from the AWSOM.org website from this link or directly from the Pixgallery Product page. This beta does not contain any new features, but is a test of a fix for people using Pixgallery on Windows IIS servers with Fancy Permalinks enabled. (so you Linux people can skip out on bothering with this version) I will stress that this is *really* beta code since I don’t have a real test server to utilize, so please remember that. With that said, the odds are the worst that would happen is the same behavior that currently exists on some of these set ups, which is incorrect links to the images.
If anyone wants to help out and try this out on their system and send me feedback that would be a huge help to me in fixing this issue. Thanks.
Further Information For Windows IIS users and Pixgallery
After more extensive investigation it appears that Windows IIS users who are utilizing WordPress and Pretty Permalinks might need to consult the following webpage for information on a fix that is needed to fully support this Apache feature: http://neosmart.net/blog/2006/100-apache-compliant-request_uri-for-iis-and-windows/.
It appears that the use of certain standard Server variables is not followed under the standard install of Apache on Windows IIS, which causes issues when mod_rewrite (that which allows the Pretty Permalinks to exist) is utilized. This has lead to some issues using my AWSOM Pixgallery plugin on IIS servers with Pretty Permalinks enabled. I can’t guarantee that the information on actions described on the above website will correct all issues when using AWSOM Pixgallery on these types of set ups, but it’s probably most of the reason why the issues are occurring. I’ll try to see if there is anything I can do from the plugin side of things, but incorrect information at the server level makes it very difficult to compensate for this issue.