Photo Custom data fields disappeared in 6.9.16 oct 06 2018

The site for the above is SearlesShoes.com – WPPA+ is used in the OUR CATALOG, NEW ARRIVALS and SHOES ON CLEARANCE menu areas
The custom data fields descriptions are still displaying fine but not the vqalues that had been entered for them
Also, the data fields do not show up for editing when you go into album admin (except for the first photo in an album) so there is no way to see if the data is still there or to edit it
I have checked in the settings and everything appears correctly checked for dispalying and editing

• This reply was modified 6 years, 5 months ago by BCBulldog59.

This will be investiagted asap.
For the time being i recommend to revert to the previous version.

De-activate and delete the plugin. You will loose no data.
Download the previous version
And install it on the plugins page -> Upload plugin in zip format.
and activate.

Can you supply me the exact data that has been entered into the custom fields that does no longer show up?

I did several tests and can not reproduce your problem when i enter plain text into the custom fields.

Each Shoe would have different values for Brand Color Style and Stock but an example is

https://www.searlesshoes.com/SearlesShoes/album-catalogue/wppaspec/oc1/lnen/cv0/ab25/pt1124

should have the values

Brand: Bueno

Color: Tan

Style: Dress (may not have this)

Stock: blank

Again, on the admin page for editing each shoe the custom fields only appear (after the Tags) for the first shoe in the album and are missing for all the rest.

Reinstalled past version…all info is back. Thanks

@bcbulldog59

Could you please do me a favour and try the current development version?
Same procedure.

Also, pls tell me your php version (see Photo Albums -> Settings the settings page, in the header)

Current php version is 5.6.36….I can upgrade to v.7 if that is part of the issue
I am out of town for a day so will test out the development version when I am back home Monday

The current development version should work on php 5.6.xx because there is a workaround in it. I would like you to test this version for other people who can not upgrade to php 7.

After you confirmed that it works, i recommend you to update to php 7 anyway, but then i know that it is safe to release the workaround (in 6.9.17).

In 6.9.17 the php version is examined, and the workaround is only used when php < 7, so that version should work always, and should also be safe on any php version.

I saw that you posted the new update 6.9.17 on Oct 9 – I am guessing this is the same as the development version you mentioned – I have tested it and it does work with php 5.6. I have since updated to php 7.2 and it is working fine