plimfec

I understand. Thanks for your answers, and the great plugin.

Plimfec

Hi,

Well, that’s a relief, thanks!

Only thing I still wonder: why wasn’t this in my logs before? The last column was always empty, for years. I didn’t even know that column existed. Weren’t the earlier attempts unlocked then? Or is it a feature in the new version?

Screenshot:

View post on imgur.com

Thanks again,
Plimfec

Thanks very much for your reply. In the screenshots I posted, you see three columns: errors / valid with warning / valid products.

You’re right, the problem has to do with WooCommerce structured data. It’s about missing fields and ‘invalid value types’. I didn’t change a thing in the product database though, so I’m a bit lost how to solve this. I have no idea, actually.

The total number of products Google has indexed from my website btw, went in a few days from 260 to 143 now. Due to this problem, I suppose.

Would be nice to hear something from WooCommerce about this. I’m disappointed they just ignore a lot of topics in this support section, including mine.

One day later, Google warnings went from 43 to 91, the number of valid products is decreasing rapidly. So, the Google Bot is constantly finding new problems while crawling the new WooCommerce setup, I suppose.

What is causing these problems in the new version 3.6.2? I’m sure somebody linked to WooCommerce could tell, so please give some information to solve this.

Screenshot: https://i.imgur.com/1TA9Dti.png

Yes, it sure helps to save the settings after updating. Thing is I didn’t expect that and it took a little while before I figured it out. I think it is more common behaviour for plugins they remember (and save) their settings after updating?

So, there is no real problem here, just some confusion. Yes, perhaps a notice is a good idea. Not for me anymore of course, but maybe for others.

Thanks for your reply!
(and for the plugin of course)

I think I might have the same problem. Running WordPress 5.0.3, Hueman 3.4.12 and PHP 7.0. All plugins deactivated.

In IE11 I just get an empty white page like @krisdech, for both front-end and WordPress backoffice, in Chrome I get a HTTP ERROR 500.

While just using the Hueman template, all is fine. Using Hueman with a custom CSS file in a child theme, all is fine as well. But when I add a functions.php to my child theme I immediately get this error 500. Even when the functions.php is empty (besides the opening ‘<?php’).

In my log file it says:

[Mon Jan 21 23:37:34.813903 2019] [lsapi:notice] [pid 20385:tid 140390996817664] [client xx.xx.xx.xx:xxxxx] [host https://www.xxxxxxxxxxx.nl] Backend log: PHP Warning: require_once(/home/uxxxxxxxxxx1/domains/xxxxxx.nl/public_html/wp-content/themes/hueman/functions/theme-options.php): failed to open stream: No such file or directory in /home/uxxxxxxxxxx1/domains/xxxxxx.nl/public_html/wp-includes/template.php on line 688\n, referer: https://www.xxxxxx.nl/

[Mon Jan 21 23:37:34.813950 2019] [lsapi:error] [pid 20385:tid 140390996817664] [client xx.xx.xx.xx:xxxxx] [host https://www.xxxxxxxxxxx.nl] Backend fatal error: PHP Fatal error: require_once(): Failed opening required ‘/home/uxxxxxxxxxx1/domains/xxxxxx.nl/public_html/wp-content/themes/hueman/functions/theme-options.php’ (include_path=’.:/opt/alt/php70/usr/share/pear’) in /home/uxxxxxxx/domains/xxxxxx.nl/public_html/wp-includes/template.php on line 688\n, referer: https://www.xxxxxx.nl/

@nikeo
Could there be some useful information in the error log to solve this problem?

Thanks!
Plimfec

I agree, this should be adjustable without the need to change the code of the php file first. Or even in the settings of the plugin.

Btw: I’m just a user like you are, I’m not the author of the plugin ??

You could change the code in the file ‘public > class-ctcc-public.php’, adding extra classes.

Find this code:

				// The main bar content
				$notification_text = wp_kses_post ( do_shortcode( $ctcc_content_settings['notification_text'] ) );
				$notification_text = apply_filters( 'ctcc_notification_text', $notification_text );
				$content .= sprintf ( 
					'<span class="ctcc-left-side">%s %s</span><span class="ctcc-right-side">%s</span>',
					$notification_text,
					$more_text,
					$button_text
				);

… and replace it with this code:

				// Message
				$notification_text = wp_kses_post ( do_shortcode( $ctcc_content_settings['notification_text'] ) );
				$notification_text = apply_filters( 'ctcc_notification_text', $notification_text );
				$content .= sprintf ( 
					'<div class="ctcc-left-side">%s</div>',
					$notification_text
				);
				
				// Link 'Read more'
				$content .= sprintf ( 
					'<div class="ctcc-center">%s</div>',
					$more_text
				);			

				// Button
				$content .= sprintf ( 
					'<div class="ctcc-right-side">%s</div>',
					$button_text
				);	

Now use your stylesheet to add some styles to the three different parts, using ‘ctcc-left-side’, ‘ctcc-center’ and ‘ctcc-right-side’.

Hi there,

I reported the issue in Github as well:
https://github.com/woocommerce/woocommerce/pull/20650

There are different threads in Github about this. It is no bug, the Woocommerce team decided to delete the button on purpose. I can’t follow that decision. To me it is quite logical to have the ability to preview first before you publish.

So, I miss this feature very much. The removal of the button did destroy my workflow (you can’t use ctrl-z to undo changes anymore, since you are forced to publish them first).

Well, that’s it. Be welcome to promote the return of the button, in Github or anywhere else, when you miss it like I do.. ??

Thanks,
Plimfec

Thanks very much for the link, interesting. Don’t understand exactly how this will work in the future though. Do you need the glotpress plugin to actually display translations in WordPress, or is it just for translators and development?

But never mind, I will hear or read more about it later.

You’re right about the benefits of a central place for translations of course. But I must say, I’ve always loved the po/mo files, since they offer you the opportunity to make a custom translation.
I use them a lot myself. Sometimes because I think my translation is better, but for SEO reasons as well (imagine you own a Woocommerce bookshop, it’s much better to translate ‘products’ into ‘books’).

Well, ok. Any ideas when this ‘glotpress’ project will be actually available for WordPress and your plugin? Because right now, we have no other option to translate the title ‘Page’ than by changing the php file (core.php), I suppose. But that’s not a very preferable method to do it of course.

Thanks again,
Plimfec

Good point.

In version 2.90 all language files were removed by the author, but still in 2.92 all went well and the plugin was picking up the right word in the right language for the title tags. However, in 2.93 it doesn’t do that anymore.

Hopefully the plugin author will respond to this.

Perhaps give the ‘tampering with CSS’ a try? Really, it seems a lot more difficult than it is.

Search the internet for how to make a child theme and what media queries are, then read this page: https://bluecapra.com/responsive-design-wp-pagenavi/

—

I’m using just this short CSS code to make WP-PageNavi responsive:

@media screen and (max-width: 600px) {
a.page.smaller, a.page.larger, span.extend {
	display: none;
}
} 

That’s all you need ??
Good luck!

Well, that was quick! Thanks a lot.
Happy to know it has your attention.

Keep up the good work, I use your plugin with pleasure,
Plimfec

Thanks very much for your reply, good to know it actually works.

And yes indeed, this way we’re just filtering the Google Bot from the stats. It doesn’t affect the actual visits of the Google Bot to the website, so no worries.

I have the same problem. My settings are:

Settings > Basic > Tracking Mode > Client
Settings > Filters > Ignore Bots

So there should not be any bots in my stats, but there are. I’ve had a lot of visits by the Google Bot, which I appreciate, but I don’t like to see them in my stats.

Two days ago I’ve tried a workaround. I’m filtering the Google Bot now, by using the field ‘User Agents’ in the settings (meant to filter browsers you don’t want to track).

Since the Google Bot is appearing as ‘Google Bot’ in the browser field (see the data in ‘Visitors Activity’), I thought this could work. And it seems to work indeed. At least I didn’t see any trace of the Google Bot in my stats last two days.

So, this is not full proof yet, but I’d like to share the idea, since unfortunately there is nobody from Slimstat responding here.

Look here:

Settings > Filters > User Agents

Try ‘Google Bot’ there, or the name of another bot that’s bothering you. Hopefully it’ll work for you as well. Good luck.