jmoen

Stefano – Could your current version have problems with the latest version of WordPress?

I have the same problem and it is not caused by how the filename is specified.

Like others, I have tried both relative file names (not starting with /) and have placed the target file in the WP root, and I have also tried absolute filenames (starting with / and with filesystem at top of path to the file).

I notice your latest version of include me (1.1.8) is compatible up through WP 5.2.7, but I am running WP 5.4.2. I suspect others who have posted problems are also running a later version of WP than what your include me supports.

Do you plan to investigate and possibly fix include me, or have you decided to abandon it?

I hope you look into this — it’s a great plugin.

Thanks for your quick replies. I was thrown off by the PHP error message. It gave the full path of the file that it said “is not within the allowed path(s)”, except it was in the allowed path. That made me reluctant to remove the open_basedir restriction. Turns out the real problem was the lower part of the path was invalid. So the error message was misleading. PHP giving a misleading error message? Who knew?

Anyway, once I realized that, I knew the error message was bogus, so I took your advice and shut off the open_basedir restriction, and of course your plugin activated first try.

Again, thanks for your responses and suggestion.

The error message says the file raising the error is G:\PleskVhosts\mydomain.com\httpdocs\wordpress/wp-content/plugins/https://www.mydomain.com/wordpress/wp-content/plugins/paypal-wp-button-manager//languages/paypal-wp-button-manager-en_US.mo

Those are good directory names through wp-content/plugins/, but starting with http, of course the path is not valid. There is no directory under plugins called https://www…. So the error message is valid.

The problem is, with this plugin installed, an invalid path somehow is being used. Removing this plugin’s files from wp-content/plugins fixes the problem.

The key lines in l10n.php are:
$mofile = apply_filters( ‘load_textdomain_mofile’, $mofile, $domain );
if ( !is_readable( $mofile ) ) return false;

Can you guess why this plugin is causing l10n.php to try to access a bad path? Or am I mis-reading the error message?

I’ve found this plugin valuable on several sites that are a good fit for how it works. I like the extra security from storing details in PayPal and not a wordpress page that can be seen using a browser’s View Source.

It’s true it is a pain to have to create new button when something changes. Obviously if you have frequent changes, for example to price, to lots of products, you probably should get one of the many Shopping Cart apps that are available. But for many needs, this is a good plugin and I recommend it.

• This reply was modified 7 years, 7 months ago by jmoen.