Thread Starter
smrqf
(@smrqf)
Additional information after some investigations
The blocking issue is due to ‘Solid Security’ forbidding the use of method file_get_contents () with an absolute path . Using a syntax as ABSPATH.’local path’ would be more secured and compliant with security rules.
No worries — we’re here to help and will get this sorted out as soon as possible.
To better understand what’s causing the warning, could you please share a few details with us?
– What version of PHP is running on your server?
– Which version of WordPress are you using?
– What type of gallery are you working with (e.g., Grid, Masonry, Slider)?
– At what point do you see the warning message is it on the front-end, in the admin area, or somewhere else?
– Did you recently migrate your site to a new server or hosting environment?
Also, for a more in-depth investigation, we kindly ask you to open a support ticket through our local support system. Once we’ve identified the issue and found a solution, we’ll be sure to update this thread with the results for others who might face a similar situation.
Looking forward to your response!
Thread Starter
smrqf
(@smrqf)
Hello,
Thks for your quick answer .
We are running last WP release : 6.7.2 , PHP 8.1.32 on a Linux LiteSpeed serveur
The issue is encountered on Grid galleries (created with previous releases) but also on the new Fusion Grid that I tested.
The issue appears on the front end (ie : when opening Web articles including Robo Gallery).
A migration occured on a new server 2 months ago. According to the apache logs , the 1st issue was detected on April 4 at 1:39:27.
I’ll manage to open a ticket .
Cheers
Antoine
Thread Starter
smrqf
(@smrqf)
Can’t find the right page to open a ticket (1st time for me) !
Could you help me
Thks
Antoine
You can use this https://app.upzilla.co/. Please register an account, or log in if you already have one, and submit a ticket in the support section.
We’ve released version 5.0.3 with a fix for this issue. If you’re experiencing the same problem, simply update your gallery plugin to version 5.0.3 or later, and it should be resolved.
Thread Starter
smrqf
(@smrqf)
I confirm the bug fixed with release 5.0.3
Thanks for your time
Antoine
