could you please send d me temporary admin access so that I can have a look?
Hi,
I took a look again & as far as I understand the issue here, this is caused by woocommerce & needs to be fixed by them. I opened a support ticket here: http://wordpress.org/support/topic/plugin-conflict-with-leaflet-maps-marker-1?replies=1#post-4446330
best,
Robert
PS: no admin access needed currently anymore.
Thank you Robert, I will wait to hear from WooCommerce suport
Hi Carlos,
can you please download the zip-file from http://test.mapsmarker.com/changelog.zip – unzip it and upload the file changelog.php to /wp-content/plugins/leaflet-maps-marker/inc/ (overwriting the existing file).
Please tell me if this removes the warning message – if yes, this fix will officially be included in the next 3.6.1 release.
best,
Robert
Hello Robert I just replace the file and sill have the following mesaage:
Warning: Cannot modify header information – headers already sent by (output started at /home/content/55/9059855/html/wp-content/plugins/leaflet-maps-marker/inc/changelog.php:5) in /home/content/55/9059855/html/wp-content/plugins/woocommerce/classes/class-wc-session-handler.php on line 63
Changelog for version 3.6 – released on 22.07.2013 (blog post with more details about this release):
I just send you the password
Please give 2 hours It might be some changes happening from an upgrade of hosting.
Hi Carlos,
did the file I sent you fix the issue now?
best,
Robert
Hello Robert, did you enter to my site and fix the problem?
How did you do it?
Two plugings are not active now, one is not important but the second one I beleive is, the WP Security, is this one creating the problem?
Thanks for your help.
Hi Carlos,
no, it wasn’t me – didn’t have the time to login on your site yet. Anyway great to hear that it is working now 😉
best,
Robert
Wow, then did someone that works with you could be the one that enter to the site?
Someone did and make changes…
Hi Carlos,
no – just I received your access data and I didnt use it for lack of time. I would ask your provider if he had made any changes to your server configuration – this is the only thing I can think of (beside someone else working as an admin on your site) that could have lead to this.
best,
Robert
