strictly-software

The apostrophe is from the “CODE” button in this editor.

You can now get PHP 5 or PHP 7 versions (free or premium) from my site as I have edited the plugin code and put it on my server.

Check out the Facebook page to be kept informed of other changes.

https://www.strictly-software.com/plugins/strictly-auto-tags

I don’t know why my plugin was taken off this site but you can get both versions on my site https://www.strictly-software.com/plugins.

Also you should follow the Facebook page https://www.facebook.com/strictlysoftware/ and my blog blog.strictly-software.com. I currently have a broken arm and I cannot work on it.

If PHP had a way of testing if a function or modifier existed still then you could do a branch for people with PHP 7 and PHP 5 but I have tried that and it doesn’t work.

The fixes are all over the web, here, my blog, FB page and other people who have found the fix

Its very simple you just remove the old code

$content = preg_replace(“/(\.[”’\”]?\s*[A-Z][a-z]+\s[a-z])/e”,”strtolower(‘$1’)”,$content);

and replace it with the new code

`$content = preg_replace_callback(“@(\.[”’\”]?\s*[A-Z][a-z]+\s[a-z])@”,
function ($matches) {
return strtolower($matches[0]);
},
$content);

You must turn on the “Auto Discovery” option and use the test text from the admin page / readme.txt file to test it.

It should then find new tags.

Hi

Why don’t you use a regular expression to collect all the words between @<(strong|b)>([\s\S])<\/$1>@ (group 2) and then just store them all in an array and then when you update/save the post save all the words in the array as tags.

Or you could use my plugin strictly-auto-tags ( https://www.strictly-software.com/plugins/strictly-auto-tags ) which does al this plus it ranks words within headers 1-6, strong, anchors, page title and the words with the most relevance and highest score are added into the post. Plus it integrates with the Tweet BOT so your tags become #hashtags when you Tweet the post out to one or more accounts. It doesn’t always tweet depends on post content and noise words etc. Free version is on this site > https://rup.www.ads-software.com/plugins/strictly-autotags/

Thanks

Rob

I am glad you like it.

Put non case sensitive words you want to ignore in the right box a case in point you don’t want IT (Info Tech) to be logged. However sometimes you get articles with IT as in (it was a rainy day) in capitals, especially headers and titles.

So if you want to ban IT put it in the case sensitive box IT. Then only capital IT words will be squahsed.

Tags may or may not be relevant if you have “auto discovery” on as all it is doing is looking for words that COULD be important, which is why you save a draft first, then publish so you can add or remove your own tags. It looks for acronyms like GCHQ or words with multiple capitalised letters Johan Smith or Sick Evil Corporation. The words are next to each other with capital letters at the start. So it goes in the “name” basket (people, companies, corps etc). Then it scans for the number of times these words it thinks are important are used 20, 18, 4 etc but it gives them a score so if they are in a header tag <h1>John Smith</h1> it gets 100 points added, if its in the title of the post 200, in bold tags 50, anchors 20 etc.

The top X (you decide) are then posted as tags in your draft post. Add or remove words and if there are words that have been tagged such as BECAUSE add it to the noise word list.

Add any top SEO words for the site either manually in the post tag section WP – or / and in the “Top Tags” section where they get an extra 100 points added to them when scoring.

If you like the plugin please consider donating even a small amount, if I had just ￡1 from everyone downloading the plugin I would be sorted and minted but people expect everything for free nowadays even bug fixes and help when they haven’t paid me.

I have extensive debugging on my site blog.strictly-software.com and https://www.facebook.com/strictlysoftware/

Otherwise you need to give me access to your PC and logins and pay for a config voucher from the site > https://www.strictly-software.com/plugins/strictly-auto-tags (scroll to bottom).

If you are happy then please think about donating even just a small amount or a couple of quid per month. It all helps it really does.

Also which version of the plugin is it as there maybe more depreciated functions from PHP 7.

Which would mean a case of looking to see where the error line was (no), turn debug on in file and save draft post.

Might be more older /e regex type functions that I rewrote in that plugin that were removed in versions after it.

But without knowing the place the bug is happening with no info it is hard to help. There are plenty of articles on my blog and FB page about getting debug info but I cannot magically see your computer.

I would need access to it. There are configuration vouchers available for purchase on my site but from what you say about it just stopping a week ago that sounds like something you did on that day. Which means working out what you did do on that day.

Try deleting some old tags maybe your memory is not big enough and you have let it run into thousands of tags when really you just want those used a lot for SEO. Having a tag used in 1 post when you have 1000 articles is no good that is why there is the “clean up tag section” for example “You currently have 1009 tags that are only associated with 2 or less posts.” why would I need those tags. So I delete them and ensure the “Max Tags to Deeplink” is always higher and I regularly clean out the unused tags.

I will have more time to work on this soon so hopefully I can make the options better but I would be wary about it all stopping on a certain date.

Hi
I take it you have upgraded PHP to version 7?
That is why that regular expression stopped working the one with the /e at the end as its no longer supported which is why it’s been replaced with the examples on blog, FB and on this forum.
Other people had issues when upgrading to PHP 7 and it was to do with that regex.
However once they did as the many examples in this forum show and replaced that regex with the new one then it worked again.
If it’s not that you have upgraded to PHP7 then I have no clue and been provided no data or examples, line no, log file errors, or info that could help me or work out why it is not working for you but does for me and many others.
It is a case of debugging as the articles show, stopping other plugins especially anything new or those that have been upgraded themselves to see if that helps.
I don’t know the code you have added to the site with plugins and themes etc but I have the Pro one working with that new regex in it. Are you sure when you copied it you did it properly, no spaces, no symbols something that could have stopped it from being copied.
Without any data or info that is all I can assume as that is the only thing that changed with PHP 7 unless WP themselves have done something like add new code in but again I have the latest version and it works fine.
It really is a case of going backwards to see what could have stopped it working, what did you upload, change etc.
The only bug being reported on this forum which you should read due to PHP 7, is that regex and the removal of /e and they provide the replacement regex in their replies as I do on the site and FB page.
So without you doing that debugging it is impossible for me to help you with no access. Check the PHP error log files, run the class file on its own on your server e.g with correct path /site.com/wp-content/themes/sometheme/plugins/strictly-autotags.php and see if any errors come up just by opeing it. Ensure error_reporting is set to error_reporting(E_ALL) at the top of the page before trying as well.
There may be a new conflict with PHP 7 and the plugin I don’t know about but everyone so far who has done that regex fix has not come back to complain.
Let me know what you find out re other plugins interfering and re-copying that regex (no spaces at all inside the “@…@”) or the regex in the callback function either.

If it suddenly stopped tagging then some other plugin must be involved as it doesn’t just stop.

Check your error logs. Make sure you read the Facebook page on it and the blog post.

So you followed this guide > https://www.facebook.com/strictlysoftware/posts/706358129513144
https://blog.strictly-software.com/2017/01/php7-support-for-strictly-autotags.html

Other people have done it including myself and it works so it must be a bug in either the words you are trying to tag or another plugin,
do the usual debug routine outlined on those sites.

The fix works for others and me so check you haven’t put an invalid character somewhere.

So you disabled all your plugins apart from mine and did the Gitmo Kentucky post tag test at the top of your Readme.txt and admin pages?

Turn debug on in the plugins code and change it to error_reporting(E_ALL); and see what bugs happen

Thanks

Did you find the bug, or conflicting plugin?

just copy the code over the top of the old code and save the file before FTPing up.

Yes, can you not get the APACHE / PHP error logs after running to find out what the actual error message is as without the error details it is hard to debug.

Also try reading the standard debug info in the Readme.txt file (on this site as well) and on the FB page > https://www.facebook.com/strictlysoftware/ and provide the developer with useful info that will help them > https://blog.strictly-software.com/2014/04/how-to-send-developer-useful.html

It could be something your host doesn’t provide or is hostgator running PHP7 – if so read up on those errors related to it – however it could be a case of de-activating/uninstalling all plugins apart from this one and seeing if any caused a clash when running together.

Thanks

Rob

It will by default only tag the post you are working on. Only if you tick the box in admin that says re-tag all posts will it do that.

So when you write an article, save a draft see which tags come up and then add your own or remove those you don’t like before re-tagging.

If something has just broken it and you haven’t changed the plugin then go through the standard debug routine in the FAQ, Readme etc > https://blog.strictly-software.com/2014/04/how-to-send-developer-useful.html

If you have just installed PHP 7 then there will be an issue with /e modifiers in regular expressions. There is a fix on this forum.

Or go to https://www.facebook.com/strictlysoftware/posts/706339736181650

Some other setting or plugin can clash so turn off all other plugins and see if another one recently installed affected it. What errors do you get in your Apache/PHP error files when trying to run it?

Need to know the basics before being able to help

Of course the plugin won’t work with Arabic it says so on the Readme file and front page of this plugin (on this site).

It is ONLY English based as it works with English grammar and formats.

It can tag lots of posts at one time which of course will put strain on your server. It is best to let it grow by having tags added per article added. Although there are many ways to tag without affecting users – cloudflare, caching, using htaccess to limit site to your IP with a holding page as you re-tag and many more.

It can skip posts with tags or it can be set to clean it up and re-tag each posting.

I don’t know what you mean by filter.

You can chose to tag your whole postings if you wish which will take a while.

You will need to learn some basic CSS – Google it – I put classes on all my BOLD and A tags so they should be easy to target.

You need to find your themes main CSS file and edit it to add the new rules in e.g

A.StrictlyAutoTagAnchor{ color: red; }

or

StrictlyAutoTagAnchor{ color: red; }

Which I believe will make the color red for any A tag with that class on it but check as I am no CSS wizard myself.

You might want to check that the servers timeout is set accordingly as the plugin sets the timeout to give it enough time but if the server config overrides it then I cannot do much but rewrite it as you say to do lots of little batches within that timescale which could be different per user.

However this is the first I have heard of someone trying to only tag 10k posts and get a server error. I am presuming it is a timeout error but if you are using PHP 7 it might be the regex error in the thread, or something else completely.

You haven’t specified the error so I cannot tell.

Can you run it and get the error from your PHP/Apache error log and post it so we can see if it was to do with Apache or PHP settings?

The debug info required for help is in the Read me file, my blog and the FB page > https://blog.strictly-software.com/2014/04/how-to-send-developer-useful.html

It should be used by anyone reporting a bug really