Absolude path after upgrading to 3.1.17

I am having the same problem. The path seems to be corrupted after upgrading. Have you found a solution?

Hello @piv5

We’d like to take a closer look at this problem. We may need to temporarily deactivate plugins and switch the theme while troubleshooting. Would you feel OK with that? If so, please send us a bug report here: https://www.imagely.com/report-bug, refer back to this forum thread and let them know Gaby referred you.

Hello @gabyimagely

Sorry, the site is currently only on my local machine.

Operating System : WINNT (32 Bit)
Server : Apache/2.4.33 (Win64) PHP/5.6.35
Memory usage : 74.85 MByte
MYSQL Version : 5.7.21
SQL Mode : ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER
PHP Version : 5.6.35
PHP Safe Mode : Off
PHP Allow URL fopen : On
PHP Memory Limit : 256
PHP Max Upload Size : 64M
PHP Max Post Size : 128M
PCRE Backtracking Limit : 1000000
PHP Max Script Execute Time : 300s
PHP Exif support : Yes (V1.4 )
PHP IPTC support : Yes
PHP XML support : Yes

Hi @piv5,

I have pinged our developers and they have confirmed that its happening with a WAMP local server only and they are going to take a look at it in one of the future releases.

@bjweigh, can you please confirm that you are also getting this one with a local WAMP server?

I need to specify here that this shouldn’t affect an web-based sites so far.

Thanks

• This reply was modified 5 years, 11 months ago by Mihai Ceban.

Hi @mihaiimagely
I built it in WAMP64 and moved to my live site. That one is still working but and afraid to do the plugin update.
I moved the live site back to local and did the updates and lost custom css. I see the same css path as @piv5

Operating System : WINNT (64 Bit)
Server : Apache/2.4.23 (Win64) OpenSSL/1.0.2h PHP/7.0.10
Memory usage : 44.65 MByte
MYSQL Version : 5.7.14
SQL Mode : NO_ZERO_IN_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
PHP Version : 7.0.10
PHP Safe Mode : Off
PHP Allow URL fopen : On
PHP Memory Limit : 128
PHP Max Upload Size : 8M
PHP Max Post Size : 8M
PCRE Backtracking Limit : 1000000
PHP Max Script Execute Time : 120s
PHP Exif support : Yes (V1.4 )
PHP IPTC support : Yes
PHP XML support : Yes

Hi @bjweigh

Thank you so much for this information.
We’ll let our developers know about it.
Feel free to write us back with any new insight.

I’m seeing something very similar on my sites. They’re only on 3.1.11. (Tried upgrading one to 3.1.17, and downgrading to 3.1.7, and neither helped.) Several of the JS and CSS links are having ‘/wp-content/plugins/’ replaced with, in my case, ‘/var/www/html/wordpress-shared/plugins-shared/’ (a directory where most of our sites’ plugins live, so we don’t have to manage hundreds of copies of them). This was just noticed today. We updated our production sites to 3.1.11 about a week ago.

https://my.domain/var/www/html/wordpress-shared/plugins-shared/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_admin/static/bootstrap/css/bootstrap-tooltip.css?ver=3.1.11

Key environment details: Red Hat Enterprise Linux 7, PHP 7.2.16 or so, MariaDB 10.2.something. Can provide any additional needed info on request.

Hi @gabyimagely

I found out that adding new images to galleries doesn’t work anymore. It says that everything is OK but there are no the images in the folder.

Downgrading my sites to 3.1.6 seems to have solved the issue, so it’s likely that whatever’s happening was introduced just after that.

Hi @desmith

Since the problems were initially duplicated the “Absolute path issue” with Windows, we were wondering if you could take a look at your site (Redhat Linux).
We may need to deactivate plugins and switch the theme while troubleshooting temporarily. Would you feel OK with that? If so, please send us a bug report here: https://www.imagely.com/report-bug, refer back to this forum thread and let them know Gaby referred you.

Hi @gabyimagely
I just rolled back to ver 3.1.7 on my WAMP site and the custom css is working.
I note that my live site is using 3.1.11 and is working.
I also built a local wamp test site with a few empty pages and one small gallery using 3.1.14 and it has the same path problem.

Bug report sent. I toggled as many themes and plugins as I could without breaking the site completely, none of that seemed to help.

Since downgrading NextGEN Gallery to 3.1.6, making no other changes, resolved the problem on my production site, I really think it’s an issue with this plugin specifically.

If you think you’ll need access to the site’s back-end, reach out to me via the email in the ticket I sent, as it can take a couple days to grant access to our org’s single-sign-on system.

Hi @desmith,

Thanks for submitting the ticket. We have contacted you back via the ticket for the additional login details.

Closing out my part of this issue: It looks like, in my case at least, the problem appears to have been a server-side issue. (My PHP-FPM opcode cache seemed to have parts of different versions of the plugin stuck in memory; restarting the php-fpm process cleared up my problems.)

Hello @desmith

Again, thank you so much for your time.
I have updated the initial bug report with this feedback.
Have a nice weekend!