GreyDragon 1.1.19 is up

+ custom.css location moved to local/greydragon/ to comply with PWG guidelines. File should be automatically created when theme is updated. Please make sure that migration is successful as it may require adjustment of “local” Folder permissions in some cases – Fix issue when Static menu would cause misalignment of the content in 3rd party plugins – Adjust min height of the content with Static menu to better fit the screen – Fixed issue when using SEO friendly URLs would cause logo not being visible in sub pages

GreyDragon 1.0.18 is out

This is hotfix release to further fix some of the issues reported recently – Added check for custom.css being present on new installations to prevent SMARTY error – Added additional “special” pages not to display main menu

GreyDragon 1.0.17 is now available

+ Added check for anonymous users when no comments present to show “No Comments allowed” in Picture page + Added support for “Activate navigation thumbnails” option of the PWG in photo pages – Suppressed support for Exif metadata icon managed by general settings in Photo pages. This logic is managed by “Hide Exif Data” option of the theme – Fixed issue with content alignment in Calendar page when Static menu is used

GreyDragon 1.0.15 has been released

+ ADMIN: Added “Image Size” option for Root Page + ADMIN: Added “Hide EXIF” option for Photo Page + ADMIN: Help content moved into standalone template file + Added support for “User Tags” plugin + Added support for PayPal Order Cart module – PayPal entry form now integrated as a Tab or Overlay + PNG size optimization for theme elements + Improved styles of Colorbox for overlays + “Tags” picture data made optional – tab would be visible only if tags are present or “User Tags” plugin is enabled – Fixed issue with Colorbox not be referenced in some cases causing popup overlay dialogs functionality not be supported when user is not logged in – Fixed issue of breadcrumb overlap Read more…

Symfony/PHP and “Too many open files”

Symfony seems to be somewhat resource hungry under some conditions and would leave trail of PHP errors indicating that there is “Too many open files”. There are several discussions on the topic suggesting that garbage collection mechanism does not close open files in some cases (ex: ConsoleOutput code). While it is always good to clean up after yourself when working with file handlers in any code, modifying the production code to address this issue may not be quick solution. Way around it is to increase file limit in Linux Using ulimit (SSH) Note: This may not be very reliable method as most systems would not allow it. But if allowed would be easiest method to address the issue First, check what Read more…