New home › Forums › Pro Add-on › Troubleshooting › writing saturation of the wp_wpgmza_category_maps table
Tagged: critical error, database
- This topic has 0 replies, 1 voice, and was last updated 1 year, 7 months ago by mmaestri.
-
AuthorPosts
-
April 24, 2020 at 11:44 am #58944mmaestriParticipant
Hello,
when duplicating a map of only 61 markers (with the duplicate button) I get a great problem of continuously writing millions of lines on the wp_wpgmza_category_maps table of the database.In summary I have to duplicate a map of 61 markers (it) for 3 further languages (en, fr, de), but at the third map everything freezes due to continuous writing to the database.
It is already the second time that I get the site blocked up to the timeout limit.
I attach a screenshot where you can see the saturation of the wp_wpgmza_category_maps table.
The problem was detected by the critical error of the site when querying the map page (CRITICAL Allowed memory size of 268435456 bytes exhausted (tried to allocate 44040200 bytes)) where it required a huge and disproportionate memory.
I have already tried to empty the wp_wpgmza_category_maps table and realign the categories also with the new update, but the problem of saturation of the table arises again.
Attachments:
You must be logged in to view attached files.April 24, 2020 at 1:11 pm #58946PerryModeratorHi there
Thank you for getting in touch, please accept our sincere apologies for any inconvenience caused,
This was a known issue with a particular version of WP Google Maps – Pro add-on 8 which was patched shortly after the first reports came in as a matter of urgency.
Please can we ask you to either disable the plugin through the menu, or by renaming the folders, to prevent any further database writes.
It sounds like you have emptied the table out, if you have a backup we can help you restore to then we can help with that,
If I could please ask you to either open a ticket at http://wpgmaps.com/contact-us enclosing FTP details, and mark this FAO Perry, or please reach out to myself directly at [email protected] – you’re through to the lead developer, what I’d like to do is clean this up for you and make absolutely sure this doesn’t happen again.
I do hope that helps, and again, we beg your pardon for any inconvenience caused.
Kind regards
– Perry -
AuthorPosts
- You must be logged in to reply to this topic.