johnwerner
Forum Replies Created
-
I reached out to One.com again, and they just confirmed their decision to not allow access to .user.ini / php.ini and stated that they “would understand if we moved to another host”.
I gave them a 2 star review on Trustpilot and described the problem:
https://no.trustpilot.com/review/www.one.comThey just replied to the review, stating that this was newer allowed before (which is odd, because we have used this setting for years and just got blocked a couple of weeks ago), and that they kept the servers secure with SSL and with DDos protection (which means that they do not understand the threat).
It looks like a ‘no go’ for functioning firewalls at One.com.
Can the firewall be optimized by .htaccess only? (when we are not allowed to edit .user.ini, or php.ini.)
One.com replied:
“Thank you for your inquiry. I have checked with the technician and unfortunately we do not allow changes in php.ini / .user.ini. They therefore recommend checking with the plugin developer to find another way to use the plugin without making any changes to the .user.ini file.”
So, next question would be if there are any other ways to work around this.
John
We are also using one.com for hosting on all the sites this problem occurred on.
Same problem on all sites. Appeared suddenly.
Not using Wordfence Central.
auto_prepend_file is set no “no value”Thanks
Thanks.
It still do not make a readable sitemap. It generated a readable index, but the sitemaps are broken.
(The number of posts on the site is less than 300, so I don’t think limiting is necessary)Yes. Number of images was cut down significantly, and seem to be correct now.
The update fixed the sitemap. Thanks.
And now it also reports images. Nice.Weirdly, it reports 3000 images on my site, but I only have around 1000. Maybe it is reporting same image several times due to the different sized copies made by the theme?
Yes of course @bobsled, now that we know there is a bug in the plugin that will be fixed, a rollback will serve as a temporary solution until there’s a fixed update available.
But at the time of my statement, we had no reason to think that the SEO-plugin had a bug that would be fixed, did we? Rather that the fault probably had root in my user setup somehow. So, if I used rollback as a final solution, I would have to stay on the old version.
This thread was resolved at the time Mr.Tobert informed us there was a bug that will be fixed.
If he did not have a bugto fix, and I used a rollback, I could never update again without encountering the same error.
Thanks for your comment.
Thank you Michael Tobert for clarifying, and I look forward to the update.
I would like to give a tip: When you know there’s a bug, I think it’s smart to inform the users (e.g. on the dashboard or your website, facebook or pinned on top of support forum). Some people might work the problem for hours in vain, trying to figure out what they have done wrong. Just a tip.
Thanks for the suggestion system90, but if you use rollback as a solution, you can never update the plugin again. Without updating plugins you expose your site to security risks and do not get new and updated functions.