MatthewS

Thanks for answering n3rdskwat. Its by far the best plugin player I’ve come across. I do sorely wish you could find a workaround for that # sign in the URL, though, as I am unable/unwilling to have that # directory in my url. I wonder if I can redirect that from my side?

Best of luck with your endeavors, and thanks.

Yes, same problem with the pound sign in the URL, would love a solution. Thanks!

Edit: Check it out, it happens to the plugin creator’s website as well.

https://www.n3rdskwat.com/#/category/about/

I guess it doesn’t bother him?

Yes, it would be VERY helpful if a different registered user (instead of admin) could be assigned to answer tickets and receive the ticket emails.

Well suddenly after 2 days it’s working properly again. Weird. False alarm?

Woo hoo!
Bacha here’s the link: https://www.nothing2hide.net/web/wordpress-global-translator-plugin/

I have few blogs hosted on separate servers, all using Global Translator. A few days ago it stopped working on all my blogs. I get blocked and Bad translated content in my log file.

This plugin seems to be dead.

All three of my blogs (hosted on separate servers) have stopped working with Global Translator. Bad translated content, Bad or unhandled response.

Increasing the time to send requests does not help. The plugin appears to be dead.

That’s crazy! How bizarre.

Wow, Scripty. We both have that issue, very weird indeed. Have you tried my /page1 workaround?

Why is the letter D so hated?

Well I haven’t fixed this problem, but I did find a hack around to make things work.

After lots of playing around, I noticed:

https://thatcostumegirl.com/?s=dog doesn’t work but

https://thatcostumegirl.com/page/1?s=dog DOES work for some reason.

So I just added /page/1 to the searchform code, so now it reads:
action=”<?php bloginfo(‘url’); ?>/page/1″

And it works! Good enough for me. But I still have no idea what caused the problem in the first place. My best guess at that when she refers to the Dragon Con convention as D*C, somewhere that asterisk broke something. Though I tried adding asterisks to different letters in the title, body and tags, I was unable to break another letter and repeat the original problem. But hey, at least searching works.

I deactivated all plugins and still encountered this problem. Very strange!

I will look into upgrading to 2.6+.

In the meantime, if anyone has any ideas, I’d love to hear them.