wpalan
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: WordPress 5.5 update failureHi and thank you for the 3 replies to-date. In my original post, I did imply that I am not currently confident enough to update to version 5.5 manually. I am frustrated by this fact but I have never used FileZilla or equivalent. I will persevere with Filezilla to see if I can update that way and report back.
As an alternative, I really need to establish why the single-click option of updating is suddenly not working for me. Is something possibly timing out after the initial download I wonder? Can I be pointed towards somewhere in my existing setup whereby perhaps I could change a setting to see if this is the cause of the sudden lack of activity?
I do have access to my CPanel file manager which might help. I’ll look out for any ideas along these lines. Thank you.Hi Gerroald
Just reporting that as of 5th July, I still get a regular batch of blocked IP address email notifications, but it fluctuates and I only appear to be seeing single IP address attempts now. They are all blocked for 2 months and I can go in and further block them forever. I can go some days without seeing any so I guess I can live with that as Wordfence certainly appears to be keeping the site secure. I really do not know why these login attempts, presumably automated, are made as I have 2FA enabled anyway along with a very strong password but there you go!Hi Gerroald
I have disabled “Enable SSL Verification” as the other option was already disabled so I will monitor performance and let you know what happens. Many thanks, Alan
Posting closed
Hi Gerroald
Thank you for coming back to me. Since my last post, I went into my Wordfence Brute Force settings and added all the invalid usernames that had been used in the blocked login attempts to-date.
Previously, I had checked the ‘Immediately lock out invalid usernames’ box but I had not entered any of those invalid usernames as I thought that Wordfence would block all username attempts other than my genuine username. Since I added those invalid usernames, I have only been notified of a couple of blocked login attempts so that is positive, although there have clearly been more than that in reality when viewing the Live Traffic log.
Here is an example of an IP address with three attempts using three different invalid usernames, just today as I post this.Type: Blocked
France was locked out from logging in at https://xx
25/06/2020 12:49:49 (1 hour 20 mins ago)
IP: 79.137.39.102 Hostname: 102.ip-79-137-39.eu
Human/Bot: Human
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0Type: Blocked
France was locked out from logging in at https://xx
25/06/2020 12:49:48 (1 hour 20 mins ago)
IP: 79.137.39.102 Hostname: 102.ip-79-137-39.eu
Human/Bot: Human
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0Type: Blocked
France was locked out from logging in at https:/xx
25/06/2020 12:49:48 (1 hour 20 mins ago)
IP: 79.137.39.102 Hostname: 102.ip-79-137-39.eu
Human/Bot: Human
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0It is those entries that show blocks of more than one attempt at the same time-stamp which I find concerning. Also, there are some entries which are marked in yellow as type ‘Warning’ which I would also like to understand as I believe they should all be blocked if attempting to use invalid usernames.
Thanks, AlanAll makes sense thank you Sybre. I have now resolved the HTML issue within Google Search Console so all looks good!
Hi Sybre
I did remove the robots.txt from the root folder and have seen the correct virtual version so I’m happy with that!
Thanks for being there.Forum: Plugins
In reply to: [Ocean Extra] Publishing failed on new page additionHi Amit, it is simple in that every time I add a new page to my website, (WordPress Dashboard/Pages/Add New) as soon as I press ‘Publish’, I see the error ‘Publishing failed’ but the page is actually fine and published.
If I remove the Ocean Extra plugin and repeat this process, I do not see the error.
I am not planning to add further pages for the foreseeable so this is not an issue for me but I just wanted it to be known as an anomaly.
After that initial step, all updates to a page via Elementor Pro are fine without errors.
Hope this helps.Hi again Sybre
The three sitemaps present in my Google Search Console, each refer to one of the three active pages on my site. From what you are recommending, I should remove two of them, just leaving the Home page version (which links to the other two).
If that is correct, I will action, which just leaves me with my main query which was asking, why would my single /sitemap.xml be reporting as being HTML, thereby throwing up an error in my Google Search Console? I do appreciate the non-importance of this sitemap but just wanted to understand how I could correct this detail. I like things to be tidy!
Thank you Sybre for your kind help.Hi Sybre
Thank you for coming back to me.
I was just looking for confirmation that my robots.txt file which is located in the root folder of my website was fine to leave, as I initially thought that if TSF could not control the settings for it, then that might be detrimental. Having since stripped off the two reference lines to Attracta SEO Tools and aligned the ‘Sitemaps’ line to my own URL, I presume that should be okay now. That’s all I need to know, thank you.UPDATE: Having logged back in later, the revised robots.txt file is now appearing when I click on “View the Robots.txt output” so please ignore my last paragraph above.
Forum: Themes and Templates
In reply to: [OceanWP] Elementor header fails to display in OceanWPHi Amit
No, I haven’t added any page level settings via OceanWP settings metabox.
This is quite a mystery as the header does appear if I view in TwentyTwenty theme.
I am rather disappointed as having first created a footer via the Elementor Theme Builder, that worked like a dream so I cannot understand why the header doesn’t work in the same way, knowing that I created it correctly.
Because I didn’t want to waste any more time in Maintenance Mode, I simply binned the header and have replaced it with my logo and a drop-down NavMenu instead which works absolutely fine. I don’t think it is compulsory to have a header element on my pages as such, so this alternative appears to be a good solution.
I still would have liked to have solved the mystery though, just for my own experience!Forum: Themes and Templates
In reply to: [OceanWP] Elementor header fails to display in OceanWPHi Amit
Thank you for coming back to me.
In answer to both your questions, I was using the Elementor theme builder header template and I simply followed the simple steps to add a header, (Add new) I then naturally chose a Header template type, gave it a name, clicked ‘Create’ and from ‘Blocks’ selected my required header design, added my logo and published and saved for ‘Entire Site’.
Strangely, the header seems to appear if I temporarily switch to TwentyTwenty theme or indeed my previously used Avada theme so it would appear as though it is something specific to do with OceanWP theme in this instance which surprises me.I have this outstanding issue along with one other whereby if I create a new page, when I click ‘Publish’, I see ‘Publishing failed’ although the page is saved fine in fact. In that case, just deactivating the Ocean Extra plugin stops that error message occurring. Very weird!
Forum: Plugins
In reply to: [Ocean Extra] Publishing failed on new page additionThat’s interesting as I already had the Health Check plugin installed and active so I used it to switch to Troubleshooting Mode as advised. Having started with the default TwentyTwenty theme and worked my way through adding my other three plugins one by one with no issues, I switched to my OceanWP theme which is the one I wish to use and all was well until I added back the Ocean Extra plugin which sadly is all but essential when working with this theme. It was then that the ‘Publishing failed’ error returned so I am not sure where that leaves me. Is it possible that the theme is PHP 7.4.5 compatible whereas the associated plugin is not, whereby that might be causing this? I guess it is not what I would call a ‘fatal error’ because following the error message, if I immediately then change the layout of that new page to ‘100% width’ for example and hit ‘Publish’, it then confirms with ‘Page Published’ so apart from the initial new page creation step, all appears to be well from then on.
What would you recommend under these circumstances. I thank you both for your kind input.