I grouped the loop block so that I could add a css class in the "advanced" field, and the interface won't reload the page in the backend anymore. The frontend page still works (the homepage), but I can't edit it, only getting a 404 error.
lien caché
Hi Conrad,
Thank you for getting in touch.
Would you mind allowing me to have admin and FTP access to the site so that I can check on this for you ?
Also please send me a link to the page where I can see this 404 issue.
Thanks,
Shane
Hi Conrad,
Thank you I was able to see the issue.
Would you mind if I took a copy of the site to test here locally ?
Perhaps there is some error being generated and would like to test further.
Please let me know.
Thanks,
Shane
No problem. Hope you can find the bug!
Hi Conrad,
I was able to see the issue on the local copy.
Could you disable the blocks plugin and then delete the block that is having the issue and remake it.
And can you run me through the steps of how you created the issue. I need the exact steps because I want to try replicating on a fresh install.
Thanks,
Shane
Shane,
I deactivated the blocks plugin, and deleted the block. After reactivating the plugin, I went to the page to recreate the block, but it was still broken. I also tried to rewind the page to a version before the error occurred, and though I can still successfully interact with the page in the front-end, I still cannot edit it in the backend.
Hi Conrad,
I need the exact steps that you did so that I can attempt to replicate the issue. I will like to see if this is replicable on a fresh install. If it is then this is something I will need to report.
Thanks,
Shane
The last thing I can remember doing was to select the view block and convert it to a group block so that I could add a css class in the "advanced" section on the right.
I tend to save and refresh for every step I do, so changes I had been making before then had applied and not broken anything before then.
I've circumvented the issue by recreating the page completely and replacing it. But let me know if you can reproduce the original issue, and if it represents a bug that I should avoid.
Hi Conrad,
I can confirm that this is in fact a bug and I was able to replicate the problem with your instructions.
What i've done was to escalate your ticket to our 2nd tier supporters for further debugging on the issue.
I will provide an update as soon as a check is done on the issue.
Thanks,
Shane