gantry5
gantry5 copied to clipboard
Compatibility Bug with J2Store & Gantry 5 Inherited Particle and Section Issue when clicking cog wheel
Hello, I've found a bug.
There's an issue after installing J2Store on a website that is using the Gantry 5 Framework. When you try to click on a "cog" for a Gantry 5 particle or section that is inheriting it's settings from another layout. You end up getting the errors seen in the images below. If I uninstall J2Store the problem goes away.
It happens with PHP v8.0, v8.1, & v8.2. Latest version of Joomla 4.x & 3.x I've tried going back several versions of Gantry 5 but nothing changes. The issue is still present with J2Store going back to v4.0.0. I don't know what the incompatibility is, or who's side it is on, I just know it exists and this error happens when both are installed.
On Joomla 3.x you see this:
On Joomla 4.x you see this:
Hi N8Solution, I think this case is related to Session Expired https://github.com/gantry/gantry5/issues/2888
Hello @tonamphong, Unfortunately this is not a session issue. It is a similar error message to the issue you shared, but I tested this out immediately upon logging into these testing sites and even the live sites.
Thanks folks. Definitely needs urgent investigation. Will check and let you know.
Hey @N8Solutions i have tested this on several installs and can't replicate the issue? Are you sure you're on 5.5.17? Because I believe I saw that error before.. Any chance that you can send me your whole install with db si I can recreate that myself?
@hexplor I've edited the Title and my original Post for this issue.
It is related to J2Store. It shows up as soon as you install J2Store.
I've opened an issue about this with J2Store as well, https://github.com/J2Store4/j2store4/issues/46
@JoomFX I'm tagging you here as well so you can be aware of this issue since you have a Joomla + Gantry 5 + J2Store template named Delight.
Yep, @N8Solutions is right. I was able to reproduce the issue. Here's a short video.
@hexplor I know you are busy with Gantry 5, but if you have the time, could you take a look at this https://github.com/J2Store4/j2store4/issues/46 to see if you can figure out what the issue is? It is clearly a J2Store issue, but they seem to be overwhelmed and understaffed.
kind regards,
Michael