[WebshopLogic]

Hi Amnon,

The slug of custom tab types that you have created have improper slug. Please change it, and the problem will be resolved.

You can find information about slug settings in the plugin documentation, in “What can be the slug of tab types?” section here:
http://webshoplogic.com/product/woocommerce-custom-tabs-pro-plugin/#tab-faq

You can find additional details about it at the last post of this thread:
https://wordpress.org/support/topic/printf-functionprintf-too-few-arguments-in-class-wp-editorphp-on-line-233?replies=3

I hope this will help to solve the problem.

Peter Rath
WebshopLogic

[WebshopLogic]

Hi Roy,

These are unusual errors, we and other users have not experienced it before. The problem may be in your wp environment.

Please try to delete all WRI and Yarpp files and reinstall them, maybe there was an installation problem.

It is also possible to have a plugin collusion. Please deactivate other plugins and check if the problem still exists or not.

If the problem stil exists, please let us know it.

Thanks in advance.

Peter Rath
Webshoplogic

[WebshopLogic]

Hi Valentin!

At this moment this plugin is not compatible with WPML.
We are working on the compatibility, when it is ready, we will let you know this.

Best Regards,
Peter Rath
WebshopLogic

[WebshopLogic]

Hi Janie!

In this case post 1 and post 3 is not related, just post 1 and 2 and post 2 and 3. That is why it is not displayed.
You should set relationship between post 1 and 3 to make it related, or use other similarity (e.g. common category) to make them related.

Peter

[WebshopLogic]

Hi Richard,

In earlier versions of the plugin was a similar saving problem.
The latest version is compatible with WP 4.1.5.

Please ensure that the latest version (1.0.16) is used.

If not, please update it (latest version can be downloaded form My account menu from webshoplogic.com).

Peter Rath
WebshopLogic

[WebshopLogic]

We discussed it in private mail, the solution was the following:

We have modified wp-related-items/wri_template/template-wri-woocommerce-loop-shop.php, and inserted these lines:

global $woocommerce_loop;
$options = get_option( 'wri_related_items___product' );
$woocommerce_loop['columns'] = $options['thumbnail_columns_number'];

These lines was inserted after this line:
if ( ! defined( ‘ABSPATH’ ) ) exit; // Exit if accessed directly

These modification will be in the next release of Pro version.

[WebshopLogic]

Hi Emilien!

I cannot find the attached PDF file.
Please attache it one more time, or send it to info@webshoplogic.com

Thank you in advance.

Peter

[WebshopLogic]

Hi Edmondo,

This plugin is works with WooCommerce product image lightbox.
If you deactivate our plugin, then the content that you inserted into the tabs also deactivated, so I suppose not the plugin, but the content is wrong.
Please try to remove every special content from the tabs (especially Google Maps), maybe this is in conflict with WooCommerce lightbox.

In our site you can see that lightbox and tabs work together without problem.
We have successfully tested the latest versions together: WordPress 4.1.1, WooCommerce 2.3.8 and Woocommercer Custom Tabs 1.0.17. The lightbox works without problem using these versions too.

So something is wrong in your environment, maybe tab content, but we have not got enough information to find the exact reason.

I hope this information is help you to find the problem.

Peter

[WebshopLogic]

Hi Craig!

Sorry you for the late answer.
I see that you can solved the problem, thank you for your feedback.

Yes, sometimes some CSS adjustments needed for the right look and feel, because every theme is different, and they are modify the appearance of Google CSE search field and button differently.

Using CSS you can achieve other appearance, so you can make more adjustments. However Google CSE has a rather complex html structure for displaying search field and search button, so sometimes it is hard to find the most appropriate CSS settings, but it ensures a wide range of displaying possibilities.

Peter

[WebshopLogic]

Hi,

I suggest you to switch on one or more of the following settings on the plugin’s settings page:
-Disable YARPP related.css stylesheet
-Disable YARPP widget.css stylesheet
-Disable WRI styles-wri-thumbnails_woocommerce.css stylesheet

In this general purpose plugin, we try to apply built in css stylesheets that is right for most sites and most themes. But of course in special cases there can be conflict between the built in css stylesheets of the plugin and your stylesheets of your theme. That is why these settings are made.
If you disable these stylesheets in the plugin using the settings above, your theme or custom css stylesheets are responsible for the appropriate formatting of related items, and you have the possibility to apply some more custom css that fit to your formatting needs.

I hope this information is help you to solve the formatting problem.

Regards,
Peter

P.S. A similar (or same) question was answered here:
https://wordpress.org/support/topic/seems-not-to-work-with-wc-23x?replies=2#post-6754789

[WebshopLogic]

Hi Abhijit!

You can apply look and feel changes using Google CSE admin page. You can find screenshots about it here:
http://webshoplogic.com/product/wp-google-search-wordpress-plugin/#tab-faq

Google Custom Search field and button contain more css elements, so I cannot write a html id or class. But if you right click on the appropriate html element in your browser and chose “Inspect element”, then you can see the html code and find the class names or ids. If you move your cursor on the html code, the corresponding html element will be highlighted in the browse.
Sometimes it is not so simple, your site designer may help you.

Peter

[WebshopLogic]

Hi Marc!

Thank you for your feedback.
Can you send us the code that you modified exactly, then we can build it in the next version to support ACF Pro.

Please send it to info@webshoplogic.com

Thanks,
Peter

[WebshopLogic]

Hi Marc!

ACF Free can be include in other plugins, we have done it according to the ACF documentation.

I do not have information about
-if ACF free and ACF PRO is compatible or not (so ACF PRO can substitute ACF Free or not),
-if they are not compatible, ACF Free and ACF Pro can be installed on the same system or not
If they are not compatible and there is collusion between Free and Pro, than we have to ask ACF support.

But first I suggest you to “turn off” including the built in ACF free version, and if ACF PRO and ACF Free is compatible, than your ACF Pro will work with our plugin properly.
I have tried it with ACF Free (I do not have ACF PRO), so I installed ACF free us a separate plugin, and “turned off” built in ACF Free. This way our plugin worked properly with separate ACF.

To “turn off” built in ACF, please delete these few lines from your woocommerce-custom-tabs.php file (before it you can copy this file as a backup):

if ( ! class_exists( 'Acf' ) ) {  //if ACF plugin is installed, it is not needed
	
	define( 'ACF_LITE', true ); //remove all visual interfaces of ACF plugin
	include_once( 'advanced-custom-fields/acf.php' );

}

There is another ACF plugin included in our plugin: acf_field_wp_wysiwyg_plugin
I do not have information about if it is part of PRO version or not.
If after removing the above part of program does not solve the problem, you can try to delete these lines too:

if ( ! class_exists( 'acf_field_wp_wysiwyg_plugin' ) ) {  //if acf_field_wp_wysiwyg_plugin plugin is installed, it is not needed

	include_once('acf-wordpress-wysiwyg-field/acf-wp_wysiwyg.php' );

}

If it is does not solve the problem, then please let us know it, and we will ask ACF support team about this.
If it solve the problem, we can make a new checkbox that enable/disable ACF Free include.

We look forward to your feedback.

Best Regards,
Peter Rath

[WebshopLogic]

Hi Nir!

Thanks for the information.
I think the problem is applying improper slug for custom post types. It is important to use always proper characters in WordPress slugs.
You can find information about this in the plugin documentation, in “What can be the slug of tab types?” section here:
http://webshoplogic.com/product/woocommerce-custom-tabs-pro-plugin/#tab-faq

Some more information about it:
Custom tab types are handled as WordPress custom content (custom post type), the code of custom tab type is a WordPress “slug”, generated by WordPress.

Slug is a text that can be part of any URL-s, so it must not contain special characters that can not be applied in URL-s. If it contains special characters, the links will be invalid and cannot be applied properly in different parts of the system, including our plugin.

Depending on your WordPress version slug can be modified (in case of oldest WP versions), but in latest WordPress versions it is not editable (as I see).

If you use a WP version that allow changing slugs, please ensure that the slug of the tab types does not contain invalid characters.
If you use a WP version that does not allow changing of slugs manually, than I suppose the generated slug will be valid and applicable in any URL. I have tested it using special characters, and it is converter automatically to ascii characters by WordPress. (Slug generation is a WordPress feature, and not the feature of our plugin).

You can find more information about WP slugs here (including “How to change post slug?” section):
https://rtcamp.com/blogger-to-wordpress/tutorials/user-guide/permalinks-and-slugs/

I hope this information is helpful, and you can set the proper slugs (according to the plugin documentation), that solve the problem.

If you have more question, please do not hesitate to contact us.

Peter

[WebshopLogic]

Ok, we are happy that you can solve this issue.

Peter

[Author]

Posts