Tanya

So under Settings / Advanced… I turned OFF mailpoet’s cron (unchecked the box) and that seems to have got my newsletters sending properly. This might be free support – but a quick suggestion to try that setting on and off would have been nice…

I have followed all of the steps in your article:
https://support.mailpoet.com/knowledgebase/my-newsletters-are-not-being-sent/

meeee tooo…. having any luck yet?

Please let me know if you find a solution to this. I’ve been on the hunt too. This is the best I’ve come across so far: https://simplemaps.com at least from a user-experience, but I’m not a programmer, so not sure if it meets your specific criteria and it’s not free. Ideally I’m looking for one that will zoom to the city and town levels, not just states and provinces….and free would be better ?? at least for now lol.

Well couldn’t find any information on this one, so I just deleted the entire plugin through my cpanel, which fixed my site.

No clue why it suddenly happened. The site was working fine this afternoon, no one was working on the site and then suddenly – poof – it was broken. Doh well… 6scan is gone now and I won’t be using them again. That kind of unreliability and lack of support response from their site isn’t something I have time to deal with.

Ciao all.

I have the same problem:

Warning: require_once(admin/includes/common.php) [function.require-once]: failed to open stream: No such file or directory in /home/gazette/public_html/wp-content/plugins/6scan-backup/6scan.php on line 32

Fatal error: require_once() [function.require]: Failed opening required ‘admin/includes/common.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/gazette/public_html/wp-content/plugins/6scan-backup/6scan.php on line 32

but – I’ve searched my FTP and I don’t have a file called “6scan-protection” that I can rename – doesn’t exist.

Help? My entire site is down: https://www.gatewaygazette.ca

Thanks, Tanya

I’m having the same problem with my site – hoping to see a response here.

https://gatewaygazette.ca/wow-what-a-summer-weve-all-had/

I’ve applied my work-around to this problem so that the search is working properly on my site…. however…. if anyone should happen to come across this post and is interested in troubleshooting what actually causes this anomoly to occur feel free to leave a comment and I’ll set it up again so you can see for yourself what is happening.

I’m fine with the work around, but the fact that I cannot name the Title of this page “Sheep River Library” and must change it to “SRL” (or something that doesn’t contain those words) indicates that there is a bigger issue at hand. Just hope it doesn’t cause other problems down the road. ??

Cheers!
Tanya

Note: now that I know I can basically turn this problem on and off by changing my page Title, I have set it to “SR Library” for the moment. So now, if you go to https://gatewaygazette.ca and search the word library you will see what I was talking about in my original post.

I’ll leave it like this until tomorrow so that anyone who comes across this topic can see what’s happening – I really would like to know what might be causing it.

But tomorrow I will need to just use the work around of a different page Title to stop it from happening if there isn’t a proper fix for it.

Thanks!

Thank you Krishna. I continued troubleshooting after posting this topic and in the end I deleted the original page and created a new one. The problem was arising when I added the word “Library” to the page title. I’ve left the url the same at https://gatewaygazette.ca/sheepriverlibrary/ but instead of having the page Title as Sheep River Library, I’ve changed it to SRL and the problem corrected itself. I can’t say that it is a proper “fix” but it is a work around and I needed it to be functioning properly right away so it will have to do. But I still find it bizarre that if I leave the word “Library” in the page Title, then the problem as described above continues to happen. It really shouldn’t matter what my page Title is, an internal search should still display the results on the normal result page.

It just happened that I only just managed to get it working properly when you went into it and tested it, so you didn’t experience the odd result. But thank you for taking the time to check it and respond.

This page is an independant landing page for our local library to set as the home page of the browsers on their public computers, so the Google search box is functioning as it should, this page isn’t intended to keep people in the primary site of https://gatewaygazette.ca. **Correction** I was curious by your comment and now see what you mean – grrr – guess I’m not finished with this one yet *sigh* – thank you for bringing this to my attention. **Phew, that was an easy fix – this is now working properly too**

Thank you, but no, I’m not working on a Mac…. perhaps one day, but not this day. ??

It’s amazing the information that can be packed into a single word! I need to work on that skill lol.

Thank you!

Yes hard lesson learned…. the really sad part is that I should absolutely know better lol. I appreciate your effort to cheer me up. ??

Being Sunday night I didn’t try to contact my hosting service & I’m one of the those impatient people, so I just went ahead and rebuilt it.

But you’re absolutely right – it was WAY faster to rebuild the second time and I did fix a few things along the way. I’m fairly new to WordPress so spent a lot of extra time “learning on the go” (apparently a bit more time on that side of it than I had realized lol) – which obviously I didn’t have to redo (thank god lol)… So my initial panic wasn’t all that bad in the end.

But figured this post and the resulting responses could still be helpful to others.

I must say that I agree with others in this forum though that WordPress really should do something about that little error being so damned easy. I had no clue that changing the URL info under “Settings” could possibly do what it did – there really should be warnings on it.

Doh well – hopefully some people will see stuff like this “before” they’ve made the error.

Thank you for responding!