• Priority: 0
  • Status: Closed
  • Theme: Alysum
  • Assigned To: Marek
  • Private: No
  • Open Date: 21.08.19, 17:13
  • Opened by: Lisa Keeling
  • Closed by: Marek
  • Closed on: 27.08.19, 11:48
  • Reason: Closed
  • Comment: Glad to help!

Ticket #15376 - AMP Page Builder Issues

Hi Marek,

There’s something not right with the updated by AMP page builder.
We’ve been getting a bunch of errors for some time on debug mode and I thought that’s an issue created at our end. So I uninstalled the AMP modules (pk_amp / pspagebuilder) - the website worked fine after uninstalling - and installed these directly from themeforest (version 5.3.7).
When I uploaded pk_amp module the website worked fine, after installing pspagebuilder the website looks like on the attached image.

dev.londoncopyright.com

Comments

Marek 22 Aug 2019, 12:33

You had to ask me before this action, but ok.

I have no access to modules section to reinstall Page Builder

Lisa Keeling 22 Aug 2019, 12:41

Hi,

What do you mean by ‘before’? We discovered it couple of days ago. I had to uninstall amp modules as we were getting those errors on debug mode and we thought those are caused by other module we purchased some time ago.

I gave you the admin access. Please try now.

Lisa Keeling 23 Aug 2019, 10:19

Hi Marek,

I’ve noticed that the dev site works fine now, but when you click on AMP setting under design you get this error..
I don’t know if you still working on it, just sending so you know.

Marek 23 Aug 2019, 18:18

Try to use the latest AMP version https://www.dropbox.com/s/zvudf2dgo71vfi8/pk_amp-v.1.0.8.zip?dl=0

Lisa Keeling 27 Aug 2019, 10:47

I installed the module, cleared cache, still see the error I sent above

Marek 27 Aug 2019, 11:33

You forgot to install Page builder module. I just did that for you

Lisa Keeling 27 Aug 2019, 11:45

I just checked the back office and the error is still in AMP setting section.

Marek 27 Aug 2019, 11:47

I do no see it. Please take a screenshot

Lisa Keeling 27 Aug 2019, 11:47

Strange, it disappeared after changing the mobile url to ‘m’

Works now. Thank you.