Jeremy Saxey

When you click the button to close the menu, just leave it closed and it should stay that way between page loads until you click to slide it out again.

FYI, WP Engine support had an interesting suggestion. Elegant Themes don’t update by themselves, the Elegant Themes Updater plugin is required and handles the updates. WP Engine suggested that looking into that plugin probably has all the info you need to work with their themes. In fact, there may even be a simple hook that could allow it to update occur. You can download the Elegant Themes Updater plugin here:
https://www.elegantthemes.com/downloads/elegant-themes-updater.zip

Just a thought. Also, no word from Elegant Themes support yet.

I’ll report this to Elegant Themes support and link them here.

So you’re saying WordPress itself is getting confused by which theme is updating and all of that to produce this confusing email with misleading info?

Update: I’ve reported it to Elegant Themes support and directed them here. *crosses fingers*

I got the above issue working on a particular install and it wasn’t a WP Engine issue for that particular item, however, I tried to use this plugin on a new install and there is a WP Engine configuration change needed to make this plugin work. According to WP Engine support:

we have to rewrite the port being used by cron jobs to allow it to skip caching, and interact directly with the server

Once they wrote that NGINX configuration to the install, it began working. Now that I have this rule in place on one of our installs, support said that I can easily have them enable the use of this plugin on future installs by simply using WP Engine support chat and state:

Copy the NGINX Before rules from the install [install name] to the install [new install name].

I tried that wording via chat and it worked great!

Also, I’ve shared the link to this support thread with WP Engine support so they can add anything useful for WP Engine customers that want to use this plugin.

If we decide to move beyond the testing phase of this plugin and decide that it will be our tool of choice, then we will be incentivized to improve it ?? So we’ll let you know. We’re still at an early phase in this process and need to figure out other pieces of the puzzle on how this would integrate with our larger processes and systems, so it may be a bit before we move forward.

For now, we are using your plugin on a few test sites and going from there.

Thanks again.

Thank you. I look forward to a future update with a bit more clarity on the options. We are considering this plugin on dozens of sites that we manage. It would be nice for our staff to be able to immediately understand the plugin without a lot of training/documentation.

Keep up the good work.

Thanks!

I think I get it now. The “Major Releases”, “Minor Releases”, and “Development Updates” are referring to WordPress Core.

So you’ve essentially disabled WordPress Core automatic updates with the plugin but allowed Plugin and Theme automatic updates.

It might be helpful to label that section as “WordPress Core” so it’s clear that “Major Releases” refers to WordPress Core only and not “Major Releases” of plugins. I was a bit confused by that.

Also, the Global Settings area, I’m guessing the setting for “WordPress Core Updates” that is still enabled there (in your screenshot) is not actually enabling Automatic Updates (since it’s the section below), but just showing that an update is available for WordPress Core (as it states in the italicized text). The confusing part there is why that needs to be enabled for the plugin to work at all??? It’s specifically saying to show WordPress Core Updates or disable showing Core updates. What does that have to do with the plugins or themes?

Thanks so much for your help. I think I am all set up, but was just giving points of clarification on what all settings are doing.

Ronald,

Thanks for the response. So I’ve done what you said and I do see that on the plugin dashboard under “WordPress Updates”, “WordPress Core Updates” are ON by default. The confusing part was that this doesn’t have anything to do with AUTOMATIC updates, correct? So what are those settings doing then? I’m not understanding what the difference is between turning on “Updates” vs “Automatic Updates”

And if I understand correctly, then this plugin doesn’t have the ability to just auto-update plugins and themes only, and NOT auto-update WordPress Core?

I posted on that thread.

I was asked to post on this thread instead, although I don’t know that this issue is a conflict with WP Engine (maybe). But I’m working with the same Brandon T from WP Engine support that fixed this issue 5 months ago.

I’m on WP Engine and have checked the wp-config.php file and autoupdates are not turned off there. I turned on auto-updates in the plugin for themes and plugins. But I left WordPress Core updates off because WP Engine handles Core updates for us and in an automated fashion with a script that checks the update worked successfully and all of that. So I want the plugin to handle plugin and theme updates but not Core updates.

The updates weren’t working and I worked with WP Engine support and they finally found that if they turned on Core updates in the plugin, the all the plugin updates started working. But if Core updates are turned off in the plugin, nothing updates.

WP Engine seems to think this is a bug in the plugin as the cron doesn’t seem to be running unless the Core updates option is on. Any insight into this issue?

Thanks for the heads up Paal!

Thank you! I’m glad too ??

Hey,

There is no “link” shortcode option in this plugin. Did you see that somewhere? Or maybe there is a similar plugin with that option?

For me, I just put an HTML link around the shortcode:

<a href="https://vimeo.com/" target="_blank">[icon name="apple-itunes"]</a>

You could add the color styling via CSS.

Font Awesome itself doesn’t offer more size options so that functionality isn’t provided via a shortcode option. However, since these are just fonts, you can just use your own CSS (in your style.css or wherever you put any custom CSS for your site) to put whatever font size you like. For example, if you were wanting to make the WordPress icon bigger:

HTML
<i class="icon-wordpress"></i>

CSS
i.icon-wordpress { font-size: x-large; }

Or you can specify the font-size with pixels or ems or anything you can do with standard CSS.

Just make sure you are properly targeting your desired Font Icon in CSS so that it only applies to the specific Font Icon(s) you want.

Hope that helps.

Not fixed yet. I have a very busy schedule and this plugin, unfortunately, has been low on my priority list. I plan to work on it more, but it is yet to be fixed.

If any devs want to help out, the plugin is on Github. Please contribute if you can.