Shortcode is not working with simple products, only on variable products

Hello there,

We hope you are doing well.

We entered your page with the problems but we don′t see any wishlist button, could you check it?

https://we.tl/t-rOl2y6SIDO

Anyways, could you test only with WooCommerce and our plugin activated with a default WordPress theme?

Have a nice day!

Hello again,

I see that my last problem is solved meanwhile Im not sure what caused it yet, but I noticed another issue for example on this page: [ redundant link removed ] the product “Cooling Peel-Off Seaweed Mask” has the attribute “data-type-product” set as “variable” and other products that the wishlist icon works for has the attribute “variation” not “Variable” for example this product on the same page “HA Intense”, they are both set from admin as “variable products”. I think that this could cause the issue why I cannot add to wishlist these products like “Cooling Peel-Off Seaweed Mask” or “Lift & Firm Caviar Mask Set” (its on the same page/link I sent you above).

Could you please guide me?
Much appreciated
Thank you

• This reply was modified 3 years, 3 months ago by Steven Stern (sterndata).
• This reply was modified 3 years, 3 months ago by Jan Dembowski.

Because the wishlist is shown only for logged in users, Im not sure how I could send you the credentials to the website since this comment will be public.

• This reply was modified 3 years, 3 months ago by claraelise.
• This reply was modified 3 years, 3 months ago by claraelise.
• This reply was modified 3 years, 3 months ago by claraelise.
• This reply was modified 3 years, 3 months ago by claraelise.

Because the wishlist is shown only for logged in users, Im not sure how I could send you the credentials to the website since this comment will be public.

@claraelise If the people supporting this plugin accept any offer to log into anyone’s site, they will be immediately banned from www.remarpro.com and their plugins will be in jeopardy of being removed.

Do not offer anyone access to your site under any circumstances. That’s not just to protect you, it is also to prevent plugin developers from some very real liability issues.

Had @silverd made that request (and they did not make that request, I am just explaining) this would have been the reply.

While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.

If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.

Thankfully are other ways to get information you need:

• Ask the user to install the Health Check plugin and get the data that way.
• Ask for a link to the https://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
• Ask the user to create and post a link to their phpinfo(); output.
• Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
• Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site vistors).
• Ask the user for the step-by-step directions on how they can reproduce the problem.

You get the idea.

We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.

When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.