Krusher

Jetpack has been causing 503 errors sporadically for the last 8 or 9 months. I use it to connect my wife’s site to WordPress.com but the last 2 updates have once again screwed up the site and cause 503 errors.
Everything is updated – latest WordPress Version, stable php (ver:5.6), latest genesis theme. Once I remove Jetpack, the site functions normally.
You guys need to get this issue ironed out – for now, I’ve uninstalled JetPack and am advising all my clients to do the same! The plugin is no good to anyone if it constantly causes 503 errors!
By the way, My wife’s site is TrendyLatina.com

Meburke, – You apparently have no idea what this plugin is for. It is simply a way to enable a pop-up or form on your wordpress site. YOUR email autoresponder (ie: aweber, get-response, mailchimp, etc) is the one that sends emails after YOU go into your auto-responder account and manually add the emails that you would like to send to your new subscribers.
There is no magic. This requires you to have a working knowledge of whatever email/auto-responder service YOU have chosen to utilize.

Don’t penalize a plugin because you don’t understand how to use it.

Hey Loneoakfbc,

I’ve setup WP-TopBar on a new site I’m working on that also uses the Divi theme.

You can check it out here: https://clearpathbycindy.com/test
I had to play with the theme customization settings to get it to work properly.

Make sure in the Divi theme options, under navigation, you have each category and page turned off or “X’d” out. If not, they will encroach on the topbar space and make it hard to see.

Also, under theme customization, under header format, I used “default” header style and checked the box for “hide navigation until scroll”.

Under primary menu bar, as well as fixed navigation settings, I used “hide logo image”.

No header elements were used either.

For a menu, I made a custom menu and included it in a “full width menu module” in Divi. Then I added a sticky menu plugin to have the menu stay at the top of the page when scrolling.

Hope that helps!

I’ve tried using the css as: font-family: ‘Petit Formal Script’, cursive; and again as: font-family: “Petit Formal Script”‘, cursive;
Both have the same result of not rendering in Firefox and Chrome.
(I know the CSS instructions on the css and html tab say that the double quotes will be changed to single quotes, but i tried anyway!)

Any idea as to how to get Firefox and Chrome to play nice with the plugin?

Thank you!

Just disable the plugin and your blog will work properly again. ??

The auto-tags plugin is broken. It’s not your site! I have it on a few of my blogs and it’s broken on every blog that I have it on. Plugin developer needs to update it to work with latest version of WP.