CustomFields are not showing.
|
maxedout
Joined: 2012-02-22
Posts: 10 |
Posted: Wed, 2012-02-22 20:15
|
|
Hello guys, new user, i know. but we had no problems with the system until an update of php/apache/mysql (huge mistake on my part, but not an option to roll back). CustomFields was working prior to the update, but then it broke after the update. we had lots of problems, but they are being whittled away. i cannot make the customfields show, i also cannot get errors to show (that could be the novice in me). is someone willing to try and help me out? let me know what else is needed.
|
|
Posts: 1153
yep, it looks like the Custom Fields are no longer displayed. Plugin/module installs just fine, added Blocks to show* in Edit Album > Theme (tab), and no errors in Site Admin > Custom Fields. It must be PHP - afaik, it was working in PHP 5.2.x just fine.
--------
Gallery version = 2.3.1 core 1.3.0.1
API = Core 7.54, Module 3.9, Theme 2.6, Embed 1.5
PHP version = 5.3.10 apache2handler
Webserver = Apache
Database = mysqlt 5.0.92, lock.system=flock
Toolkits = Ffmpeg, ImageMagick, Thumbnail, ArchiveUpload, jpegtran, SquareThumb
Acceleration = none/1814400, none/1814400
Posts: 10
yeah, the version of php i went from was 5.1.6, is there a possibility of getting this fixed? especially seeing as gallery 2.3.1 was supposed to be compatible with php5.3?
Posts: 1153
if I remember correctly, Gallery 2 development stopped, version 2.3.1 was for PHP 5.3.x compatibility, afaik. But if you can code, I'm sure the devs (and power users on this forum who know the platform really well) can walk you through or help point where exactly to look. I'm not a coder myself so I'm stuck too. The other option is to go back to the previous version of PHP but you'll be open your site to a whole can of vulnerabilities related to PHP
I can't even run the unit tests in PHP 5.3.10 anymore - for some reason I'm getting errors. Looks like I'm going to have to make a "Known Issues" list very soon for my users. I'll have to do manual testing for each module/plugin available in my local codebase.
__________________________________________________________
liberate your photos with Gallery, make the switch today!
https://pixi.me/
Posts: 10
i can plug around the code, but it isn't my forte. i can make the changes to the files, but someone would need to find where it is broken in that module.
Posts: 1153
I think you'll also have to run G2 in debug mode (there's a FAQ for it or look in /gallery2/config.php) and at the same time, look at your logs for some more hints. Try the IRC chat room also on irc.freenode.net #gallery
__________________________________________________________
liberate your photos with Gallery, make the switch today!
https://pixi.me/
Posts: 10
also, i cannot see this post in the forum's list of topics.
Posts: 27300
Interesting, nor can I. I will get Bharat to investigate later today/tonight.
Dave
_____________________________________________
Blog & G2 || floridave - Gallery Team
Posts: 10
thanks Dave.
output of debug on a picture with customfileds, while signed in as admin. i hope someone can figure this out.
location of picture:
http://motorcyclegallery.oldbikebarn.com/v/MORDERN+BIKES/2012_HONDA_CBR1000RR.jpg.html
**edit** removed debug dump.
Posts: 1642
Gallery2.3.1 is PHP 5.3 and 5.4 compatible.
A module written by a third party such as custom fields, if working with PHP 5.2 is definitely PHP 5.3 compartible.
On PHP 5.3 "compatibility", there are various levels
1. Script can be written to work with PHP 5.3 no matter what the server settings are. This is the case with G2.3.1
2. Script written for PHP 4 to PHP 5.2 is compatible with PHP 5.3 depending on the PHP error settings on the server as it it uses some PHP functions which will be removed in PHP 5.4, warning messages will be generated and what happens next depends on the PHP settings on the server:
a. PHP may be set to just continue and ignore the warning
b. PHP may be set to log the warning and continue as normal
c. PHP may be set to display the warning message and continue as normal
d. PHP may be set to terminate processing
The custom fields module, a third party effort, probably falls into Category 2 and your server PHP settings probably falls into Category d.
Options.
A. You can reset your PHP settings
B. You can edit the module code to avoid such funstions
C. You can post the warning messages from your logs here and hope someone tells you how to edit it to avoid warning messages or that they edit the module and post an update.
--
dakanji.com
Posts: 10
i do not see any errors anywhere related to php. any more specific hunting grounds?
Posts: 1642
Look in the server log.
Most hosts, if on shared hosting, give some access through the control panel.
Obviously, you don't need to post the whole log but visit the offending page and look for lines relating to php errors.
--
dakanji.com
Posts: 27300
Bharat fixed it up. Could be related to the recent multi post issues we have had.
Let us know if it happens again.
Dave
_____________________________________________
Blog & G2 || floridave - Gallery Team
Posts: 10
I looked in the httpd/error_log and there was nothing related to php. this is my frustration, i could be looking at the wrong log. php.ini is set to E_ALL for error logging, unless i misunderstood that.
@dave, thanks man.
Posts: 1153
just upgraded to PHP 5.4 - now it shows up in Edit Album > Custom Fields (Tab) and added it to Blocks to show* in Edit Album > Theme (tab)
- in PHP 5.4 (so far of what i encountered)
GD is borken (but I use ImageMagick as my primary toolkit)
got an "Error" for certain mySQL users with older 4.1 password hashing, had to update them so G2 could connect
__________________________________________________________
liberate your photos with Gallery, make the switch today!
https://pixi.me/
Posts: 1642
Nice to get the confirmation that PHP 5.4 works.
When Dev Team Member, Mindless, was updating v2.3.0 to v2.3.1 for PHP 5.3.3, he had a choice between just doing the minimum needed or going the whole hog and putting in PHP 6.0 compatibility which was the planned update from PHP 5.3 (bearing in mind that official support had already stopped for over a year I think at that time).
Anyway, after some thought and pleas, he decided to go for the whole PHP 6.0 hog. The PHP devs later suspended PHP 6.0 and rolled the code into 5.4 so thanks to Mindless (where is he these days anyway? He hasn't been active since G3).
On MySQL, there are a few driver changes and perhaps that is why some older stuff had some issues with you.
On the GD module, I'm pretty sure Mindless took at thorough look at everything so it isn't certain where any issue might be springing from. The two candidates and the PHP GD extension you have itself or the G2 interface module for GD. I'll look at it at the G2 module at some point as part of this project (or perhaps someone else can).
--
dakanji.com
Posts: 10
My custom fields show up in the edit photo, but they will not display in the front end. very frustrating. is there some code or something we can try to make it work?
Posts: 10
http://motorcyclegallery.oldbikebarn.com/v/MORDERN+BIKES/2012_HONDA_CBR1000RR.jpg.html
that is a page that should have the custom fields showing. there are no errors in my logs, no debugging errors that seems to help.
I do need to solve this, can any one help?
Posts: 1642
Most likely the theme in use does not contain the code needed to display custom fields but then you said it was showing until you upgraded php/apache/mysql.
Are you sure those were the only things you changed?
Have you tried viewing the site using an official theme such as matrix?
--
dakanji.com
Posts: 10
Yup, I am sure, i changed only those things. it was working before that. now it doesn't. it shows up in the back end, i created all the fields and then we had someone go picture by picture and edit them to add the data that we wanted to be there (motorcycle specifications) and the data is present in the backend, but does not show up to the web front end. very frustrating. i also did try the carbon theme as well as matrix, no dice.
Posts: 1642
Every such error is down to simple logical and repeatable issues.
If the code in the module is in compatible with PHP or Apache, there will be an error logged somewhere.
If you are not missing the error log file and have not switched it error logging off or disabled it in some way (fully or partially), the only reason that there will be no error logged is that there isn't a compatibility issue.
This leaves one, and only one, other possible answer ... somebody changed/edited something else somewhere.
So in summary, it is one of the following:
1. You are missing the error log file
2. You have somehow disabled error logging (maybe partially)
3. Someone with access to the server has changed something in the code
You will have to figure this yourself since you say rolling back is not an option (you could try replacing the module files from a fresh download)
--
dakanji.com