Dougal Campbell

In the User-Agent Blocklist, there is a line with the string DOC. This is what is matching against Stripe. Their User-Agent string is “Stripe/1.0 (+https://stripe.com/docs/webhooks)”, and the DOC blocker entry matches against the /docs/ substring.

Remove that line and re-save your settings. We are going to remove that entry from future versions of the plugin, as it is very generic and has too much potential for other false-positive matches like this one.

In the User-Agent Blocklist, there is a line with the string DOC. This is what is matching against DoCoMo. Remove that line and re-save your settings. We are going to remove that entry from future versions, as it is very generic and has too much potential for other false-positive matches like this one.

I see the title is now “Tekz24 | Smartphones, Apps, Games And Other Gadgets Portal”, so does that mean you figured out the settings you needed?

If you haven’t done it already, please try installing the latest version (2.3.2.3) and let us know if you have any other problems.

This problem appears to stem from a PHP host configuration where the include_path setting is used, and is set in such a way that system files are searched before the files that are local to the currently executing code. When where is a conflicting filename in the system paths, the wrong file gets loaded.

This should be fixed in the latest versions of the plugin. Please install the newest version (currently 2.3.2.3), and let us know if that resolves your problem.

Actually, nevermind about the phpinfo — I was able to duplicate the problem. The conditions for this problem were: 1) both the include_path and open_basedir directives are in use in your php.ini config, 2) a conflicting filename is found in an include_path dir (/usr/local/sb/include/init.php, in this case), but 3) that dir is not part of the open_basedir list. (whew!)

For now, if you want to fix it in the current version of the plugin, edit the all_in_one_seo_pack.php file, and change line 332 to read like so:

require_once( AIOSEOP_PLUGIN_DIR . '/init.php' );

A new version with the official fix will be released soon.

Could you add a file to your ‘httpdocs’ directory named ‘phpinfo.php’ with the following contents:
<?php phpinfo(); ?>

Then visit ‘https://www.dottorblog.com/phpinfo.php&#8217;, save the results, and post them through https://semperplugins.com/contact/

We are looking into this and trying to duplicate.

Thanks!

@djib’s, what other plugins do you have on your site? Any kind of caching?

It is not possible at the moment. It’s been on my to-do list for ages, though.

Keep an eye out for future updates.

Those are good ideas. When I get time to work on updating, I’ll keep those in mind!

I should be able to provide a way to list which fields/metadata you want to display.

Path disclosure doesn’t make a site vulnerable. Yes, it’s information that could make it a little easier for a determined hacker to find things to poke. But only if you server has a vulnerability in the first place. Security through obscurity is not security, as the saying goes. Also, the path Mike posted above is obviously on his own local dev setup, and most-likely not on a public-facing IP.

That said, eliminating all warnings and info messages is still a Best Practice. Yes, it’s annoying to error-check every instance of an array index, define(), etc. But it’s still a Best Practice. Clean code is happy code!

Oh, and nobody is advocating running with WP_DEBUG in production. But even so — many sites turn on logging for warnings or even info messages. If you leave in code that generates these unneeded messages, all those servers running your plugin will waste CPU cycles and disk space for them. I, for one, get annoyed when my logs are polluted like that.

A future version will combine everything into a single activation. I wrote the original hoping that others would write separate add-on plugins that used TFS-Core, but only one other plugin ever did that (TFS-LOLcat).

Upload images to your post, then use the gallery shortcode in your post content, like this:

[gallery link="file"]

That’s it!

Well to me GPL = Free.

(emphasis mine)

What it means “to you” doesn’t mean a damn thing to the letter and spirit of the GPL.

Surely you don’t think you’re the first to think of this, or to bring it up here or elsewhere? I mean, really. The GPL exists to protect the freedoms of the recipient of code. On the one hand, it was written in a different time for a different set of circumstances — it didn’t have scripting languages in mind where the running code is the source code. Thus, some provisions of the GPL are redundant in this context.

Yes, you can legally redistribute their code. And I’m sure you’d have a crowd of people eager to take advantage of that. But they will not have a way to verify that you haven’t modified that code and snuck something underhanded into it. I’m not saying that you would, but if you (or someone else) did, the only way to verify it would be to compare it to a copy of the code that was obtained legitimately. And what happens later when there are official theme code updates — bug and security fixes? Do you plan to keep up with those?

Have you ever coded a theme from scratch yourself? Not a child theme. Not taking an existing theme and modifying it. I mean starting with an empty directory and coding all the PHP, CSS, and JS for a decent subset of the template files and a functions.php? I did it once, just as an exercise. I still don’t consider it finished, and it was a lot of work. You put enough work into something like that, enough planning and thought, you might start to think it’s worth a few dollars. I don’t know about you, but I don’t work for free. My time is worth money. Yes, I do put out plugins, tips, articles, and such for free — but not all of my work. I don’t know about you, but I’ve got bills to pay and a family to support.

So sure, you could buy a premium theme (or obtain it for free from someone else like yourself), and redistribute it for free. But that certainly doesn’t make you somebody that others in the WordPress community will respect.

why should i pay 60$ for it i dont have so mutch money for that.

Nobody says you have to spend your money on a premium theme. There are plenty of themes out there that are free-as-in-beer. Download one of those and spend your $60 on a nice steak dinner and a bottle of wine. Or a month’s worth of mac-and-cheese. Whatever.

You could also look at something like:

https://www.ads-software.com/extend/plugins/solr-for-wordpress/

If you don’t want to try setting up and hosting your own Solr server, there is apparently a hosted service, and an adjunct plugin to use it:

https://www.ads-software.com/extend/plugins/advanced-search-by-my-solr-server/