hayesmd

Just sent through the link.

Sure, I don’t mind loading beta’s on less important sites of ours. We have 7 or 8 sites that rely on this plugin, so it only makes sense for us to do our part and help out where we can. I can definitely load it on 1 or 2 where the shortlinks get posted to Facebook daily so the writer can definitely let me know of their experience.

Sorry, that did not fix it. Hate to say but the official plugin worked just fine. I may have to enable that one for now until this gets resolved. I have this on 9 different sites, so I’ll keep one with wp_bitly to keep an eye on the issue.

Seems like this part of the Changelog may be the problem:

Removed wpbitly_generate_shortlink() from save_post

I have a hunch that when the Template plugin is bringing its stuff into the post editor is when the shortlink is created and it’s pulling the template URL and not the post URL.

Can you send me the code and location to add it and I can test if that is the problem? The version 2.2.4 or which ever was immediately before this one worked just fine.

Just noticed this but the shortlinks are different from what I get on the post and what is displayed on bitly.com as the generated link.

Either way both shortlinks go to the wrong URL.

On bitly it is showing the right URL for the post, but the shortlink goes to the wrong page on our site: https://bitly.com/1mBbEyu+

2.2 fixed it for me.

Awesome, I’ll test it now.

I added:
add_action( ‘admin_bar_menu’, ‘wp_admin_bar_shortlink_menu’,90 );
to my functions page to get the shortlink button back.

I found a work-around:
https://www.wpbeginner.com/wp-tutorials/how-to-add-shortlink-menu-item-in-wordpress-admin-bar/

Also make sure you are not trying to use the ‘Legacy Token’. Click the link provided in the settings page to generate your new token.

Jakeofthefoliage, I think you are experiencing something different from what we are talking about. We never get a true 404 error message, we get a 500 error message and can’t pull anything up on our sites for about 60 seconds because our IP address gets locked out for too many redirects.

The fact you can publish posts and you get the 404 after it is published would make me lean in a couple directions. First, check your permalink structure and second second your re-write code. .htaccess for Linux and web.config for Windows. Good luck and I hope you resolve your error.

Yep, exactly what we faced. I didn’t even push for whitelisting because we have 10 editors and maintaining their up-to-date IP’s would be impossible much less getting GD to update them for me.

As I said we were actually very successful running our WP sites through their Windows hosting and were even able to use WinCache successfully with W3T. We just had other permission type nuances pop up. Our decision to move to VPS was solely based on site growth. We also found out that GoDaddy shared hosting only supported 400 concurrent connections to all sites in the account. That could have been an issue for use during certain times a year. The VPS was a no-brainer.

At least they gave you the truth. I said I had read in forums that the above was the problem, but the reply I always got was there’s a problem with my code and since the hosting account is serving pages it’s not a server problem and that there was nothing they could do.

Oh, and for my first 3 weeks trying to figure it out they blamed it on my ISP, my browser, anything but changes they made. Even though multiple authors on our site could replicate the same problem. I even sent them some basic HTML that had 15-20 HREF’s in it and they never would try to create a post to see the issue for themselves even though their DEV’s created 2 WordPress installs in our account for testing purposes. They only ever posted ‘Hello World’ posts and not the HTML I sent them.

For us on Go Daddy we resolved it by switching over to Windows Hosting. Like I said, that resolved the internal redirect issue since Windows uses IIS and not Apache. BUT, Windows hosting opened up a whole new can of worms. We eventually upgraded and went to a VPS solution with Linux where we could leave off the mod_security module and everything has been great ever since.