lipskas

Wow, I can’t believe authors of free plugin provide such superior support. Thank you very much for super-detailed guide; will check it during weekend and let you know.

Thanks. Maybe I didn’t explain myself very clearly in the 1st post, sorry about that.

I realize the plugin supports translations, but as far I know, plugin only uses non-English translations if WP is set to use non-English language? Which brings a problem too; since many themes/plugins don’t have translations to X language (or translations are not full), many webmasters (including myself) prefer using English for backend, even if website is targeted at users from country X (especially if website has no login/private sections). This way, webmasters only need to customize frontend text (displayed to visitors) and can avoid horrible mix of translations in WP admin dashboard (which happens when plugin A is translated, plugin B is not, plugin C is translated in half, etc).

Since other plugin users raised the same question in the past (about customizing “Always active” text without using translator plugins and/or local translation files), I believe it’s important many more webmasters.

Once again, thank you for your consideration about making text customizable in future releases. Hope that happens soon. If it requires purchasing premium subscription, I’ll be happy to.

Thanks for the reply. However, it doesn’t answer the main question – why Complianz allows customizing every single piece of text in cookie banner except the most important one?

I believe that installing a new plugin just to customize a single option in Complianz is overkill.

As far I know, there were some changes in PHP 8.1 regarding HTML entities ( https://php.watch/versions/8.1/html-entity-default-value-changes ) and encoding.

Not sure if it’s the case, but https://github.com/TablePress/TablePress/blob/main/libraries/html-parser.class.php seems to use html_entity_decode() function, which was affected by 8.1.

First of all, it’s not a trouble at all. I realize this is free product and you do your best to help users, which I’m thankful for.

My first thought was also about missing modules in PHP. But I did strict comparison between my PHP 8.0 and 8.1 installations and they use exactly the same modules.

Like I mentioned, JSON continues working fine. Also, if I add text to table manually (using “Edit Table” feature in plugin), all foreign characters are displayed fine. The website itself is non-English too, and WP displays all foreign characters (even on the same page where table is inserted) just fine. Only imported HTML content is messed.

Here’s a sample file – https://ufile.io/1cypxiej

Thanks for the reply. I’m not very sure how WP plugins work, but regarding “normal” DataTables, there are no special needs for that plugin.

Integrating this particular DataTables plugin is actually a bit tricky, as it needs to be loaded in a special place (after the embedding of the normal DataTables JS file, but before the execution of the features).

I use this plugin in several scripts, and all I have to do is include plugin *.js file right after including DataTables *.js file. Once included, everything works automatically.

Thanks, that was one of the fastest responses and fixes from software developer I ever experienced.

I think there’s something wrong with version numbering. WP repository still displays it’s version 3.0, but after clicking Download button, it downloads file buttonizer-multifunctional-button.3.0.1.zip

So I downloaded this file, manually re-uploaded it and plugin started working. But it still says v3.0, not sure why it’s so.

P.S. I see that all the options are not available in v3 by default, and it only displays “Start Migrating” button (which redirects to some signup form). Does it mean I can’t use Buttonizer without creating an account with you?

Just to be sure – if I uninstall plugin and re-install it, all the settings will remain in place, right?

I knew it was risky to upgrade to a major new release right after it was published, but your reply seems to be super-fast and promising. Thanks for quick response.

Thank you for the response. I checked the tablepress_cell_tag_attributes, but I’m not sure if it suits my needs. If I understand right, I need to utilize this in functions.php? Will it work if I know nothing about table? I mean every time the table is imported, it contains a different number of rows and data is slightly different. Also, I need to add data- attributes to more columns (not just weekdays), doesn’t it mean a lot of programming is involved here?

Just updated. No more new entries in error_log file. Will monitor it for another 24 hours and will let you know if there’s something wrong.

Thank you, just did.

Logged in via FTP to one of my sites and found error_log file which is full of errors:

[02-Aug-2019 10:12:34 UTC] PHP Warning:  Illegal string offset 'width' in /home/myuser/public_html/wp-content/plugins/all-in-one-seo-pack/inc/schema/graphs/graph-organization.php on line 114
[02-Aug-2019 10:12:34 UTC] PHP Warning:  Illegal string offset 'height' in /home/myuser/public_html/wp-content/plugins/all-in-one-seo-pack/inc/schema/graphs/graph-organization.php on line 115

For some reason, it only happens on 1 site. I have another WP site running on the same server (so it uses exactly the same PHP environment), but it doesn’t show this error. According to the log, error started occurring just today.

I wouldn’t worry about it though, since I doubt casing matters here. Also, keep in mind that Google, Bing, and Yahoo no longer use keywords.

As I earned living by doing greyhat/blackhat SEO for 10+ years and switched to “normal” stuff recently, there is no single person in the world who can convince me meta keywords have 0 effect ??

Anyways… What is the exact reason why you forcefully apply strtolower to keywords? Thanks.

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