aussiemike
Forum Replies Created
-
Thank you for this temporary fix. It will do for now but does not solve the validation problem. I look forward to the next update with solution.
Best wishes
MikeI posted another request and got the same answer as usual. The developers will look into it. Even their paid members are waiting for a solution and have been for a long time. Fingers crossed we might see a solution soon.
Hello Nastia,
Thank you for your response but this appears to be the same response to the same ongoing issue. It’s not like it only happened yesterday, been a problem since the creation of the plugin. Even in your paid members forum on your own site their are requests for a solution.PLEASE PLEASE PLEASE can we all have a fix for this? Even a temporary solution would be better than waiting another year to see if it does get fixed.
Best regards,
MikeMonths later and still not fixed.
- This reply was modified 4 years, 9 months ago by aussiemike.
Same issue here. Activating the GDPR Framework plugin renders the Fusion Builder editor inaccessible and the default editor inaccessible.
Hope to see a fix as this is the best GDPR plugin available.
Avada version 5.5.2
ThemeFusion Page Builder Plugin Version 1.5.2
The GDPR Framework Version 1.0.10Forum: Plugins
In reply to: [Plugin: Extreme SEO] how can i see incoming links?I installed this plugin I was getting backlinks. Great! One thing though – my hosting company disabled it within a couple of days and sent me the following information (I would post this to the forum but cannot access the site):
NOTE: If your hosting server has a memory limit be sure to edit plugin (extremeseo.php) to reflect this limit or your hosts may disable your site.
We’ve found the following script was using too much server resource and had negative impact on the server’s performance. We have disabled the access to the file immediately (chmod 000) as it is direct abuse of the network services and a violation of our TOS and AUP.
Once you have identified the problem and optimized the script, you can just chmod the file back to 644 to reinstate its public access.
/home/xxxxx/public_html/wp-content/plugins/extreme-seo/extremeseo.php
———–log———–
May 7 08:09:10 ALERT – script tried to increase
memory_limit to 524288000 bytes which is above the allowed value
(attacker ‘xx.xxx.xxx.xx’, file
‘/home/xxxxxx/public_html/wp-content/plugins/extreme-seo/extremeseo.php
‘, line 11)
————————–Regards
Mike