jodamo5

I have found the answer!

This plugin has been discontinued, because the functionality has been released in core Gutenberg.

Here’s how to apply inline color to text or background color in Gutenberg:

1. Select the text you want to color.
2. Click “More” button (drop down arrow) in the text toolbar
3. Click “Highlight”.

4. Then choose the text color or background color.

Thanks for the quick reply John. I had already read through your documentation and thought I had followed the instructions. Specifically, I used * and not (.*) and didn’t use $1.

However, upon re-reading it, I can see the difference is that I need it to say .* instead of just *. I think this is what you mean when you say my example is using a wildcard instead of regex – I needed to add the “.”

So to help anyone else who gets tripped up on the same thing, here’s the summary:

Wrong: ^/for-people-with-disabilities/*
Right: ^/for-people-with-disabilities/.*

• This reply was modified 1 year, 11 months ago by jodamo5.

Hi. Thanks for your reply. As per my first message, I’m running the free version only. Not the premium version.

Sorry for the trouble – the crop button is now working for me within the featured image dialog. And once the featured image has been set, the “Crop Featured Image” button underneath it is working too. Not sure why it didn’t work for me at first, but a few minutes later it is all working well now.

I’m not the author, but I’m running WordPress 5.6 and this plugin works well for me. Maybe try installing on a blank WordPress install and see if it works for you. If so, that would indicate it is a conflict with your theme or another plugin.

Ok, I’ve hacked a solution with using width: 100% !important;

Not ideal, but it’s working! Feel free to close this support request as it seems to be an obscure case.

Just checking in – did you colleague manage to have a look? Any ideas on what might be causing the section to be assigned a width of only 1.8px by this plugin? Thanks.

Hi John. On further investigation I was slightly wrong. It wasn’t pulling the max_execution_timefrom a editable field, but it was pulling it from the database.

WP All Export plugin has default values built into the plugin that get inserted into the options table under this entry: PMXE_Plugin_Options

The problematic code was in this plugin file: \wp-all-export\actions\wp_loaded.php

$maxExecutionTime  = PMXE_Plugin::getInstance()->getOption('max_execution_time');
	if($maxExecutionTime == -1) {
		$maxExecutionTime = 0;
	}

	@ini_set("max_execution_time", $maxExecutionTime);

The default value for max_execution_time in the plugin is 0. And there is no way to edit that value in the free version of the plugin. (As a test I changed the value in the database and the new value did pull through).

Also is was strange to see that the max_execution_time was getting overridden on every page load and not just when WP All Export was actually running an export!

This is only happening in the free version of their plugin. When I checked the other sites we have where the issue isn’t occurring I realised that we were running WP All Import Pro. So that problem is not in the Pro version, only the free version.

I have raised this with the developers and removed the plugin from my site.

Thanks for your help and excellent support!

Thanks for the answers John. I searched all code on the site and found that WP All Export plugin had a max_execution_time override in the code that pulled in a settings field value. However, the settings field was set to 120. I decided to test it anyway by deactivating the plugin and Query Monitor now says that the max_execution_time is 150 (which is the value set in php.ini).

So it would seem to be fixed, however it seems very strange to me! For two reasons:
Firstly because WP All Export is a very robust and well-known plugin. And secondly, we use that plugin on a number of other sites, and Query Monitor doesn’t give that error on any of the other sites. All the other sites get the php.ini value for max_execution_time when WP All Export is activated. I’ve checked, and the version of the plugin is the same on both sites, and the settings are the same. So I’m at a loss as to how to explain Query Monitor reporting a problem on one of the sites when WP All Export is activated, and not on another site with the same settings in place.

If you have any further guidance, that would be great. Otherwise, we can just close the ticket. Thanks for your help.

Thanks. I have now opened up a ticket here – https://core.trac.www.ads-software.com/ticket/50100

I’ll mark this as resolved, since the problem has now been logged and will be worked through by the development team.

Thanks @jnashhawkins. Neither of those are really the ideal solution. Since WordPress has domain mapping as core, this should be fixed in core. Any idea how to raise an issue with the dev team? I’ve looked at Github, but couldn’t identify the correct place to raise the issue.

Update: I’ve found another WordPress GeoLocation plugin that gets automatic weekly downloads from the MaxMind GeoLite IP address database. So I recommend switching to that one:

https://www.ads-software.com/plugins/geoip-detect/

I run Better Anchor Links on PHP 7.0 and it works fine for me.

Thanks for the excellent reply. That fixed it. Sorry I didn’t spot the filters in the help section.

I found them in the documentation section of your site – but it was just an image, so not searchable. Now I see it is right there in the plugin! On the “Help Links” screen, alongside the “Documentation” and “Help and Support” icon sections, can I suggest that an icon section for “Filters” gets added to? That would make it easier to find for new users.

Also, just a thought – a number of the filters have example code, but the example code doesn’t actually include the add_filter line itself. It tripped me up briefly after copying and pasting the example code and wondering why it didn’t work. It could be beneficial to include the add_filter line into each of the examples.

Overall, thanks for the very powerful plugin and excellent customer support. I’ll write a review.

Cancel that … the site is hosted with HostMonster and it appears they’ve decided to push everything through a proxy server … which is causing all traffic to come from an USA IP address.