luboslives

For anyone curious about importing from another system like the Yith wishlist, the share_key need only contain the letters A-F and numbers 0-9. This was my error. My generated keys went from A-Z and so they would fail the regex requirements I found in this plugin’s source.

I think I’ve narrowed down the problem. It only exists for users from the previous version of the site who had wishlists on the old site. New users or new wishlists are working fine.

I had attempted to port over the data from the old Yith Wishlists plugin into this new system but it seems somewhere the dots weren’t connected. I tried to create a unique share_key for the existing lists, maybe there needs to be some sort of relationship in the database that I need to hook up. I will try the live chat if I need assistance, thanks.

My footer’s also been disappearing in the latest version when I switch themes – because the actual footer widgets get deregistered/removed. If your footer area is a designated widgets area, check the widgets menu to see if yours have disappeared.

Update – I’ve used the good old intermediate_image_sizes_advanced filter to unset them all by name. But I’m still curious if it’s an actual bug that the sizes remain registered.

Thanks, I tracked down the <p> problem. It’s weird it wasn’t happening when my shortcode was by itself on the page, but I had to escape the opening line of the string being output by my shortcode. That did the trick.

Edit: actually it just stuck the <p></p> inside my flex container that i escaped, so i’m no longer seeing it. Not sure if i’m out of the woods yet.

Edit 2: Yup it’s something on my end when combining more than one shortcode of any kind on the page.

• This reply was modified 7 years, 1 month ago by luboslives.
• This reply was modified 7 years, 1 month ago by luboslives.

Awesome thanks. I actually just noticed that it was only my second shortcode causing the problem.

[products on_sale='true' limit='6' orderby='popularity' order='DESC' class='cdn_product_list_home']

Looks like we get empty <p> tags after the output as well.

Sorry it’s still not displaying any custom sidebar on the shop page. I’ve even changed the dedicated shop page setting back and forth between pages, that didn’t kick-start anything.

I’ve commented out all my custom theme includes in case something is interfering, and still no custom sidebars show on the shop page.

I should have this site up in a staging area this weekend if it will help to take a look at it.

Updates:

The problem seems to be with my Shop page and any widgets within a custom sidebar. I unregistered my “Shop Pages” sidebar from the shop page and created a brand new sidebar with a simple text widget, and that text widget is refusing to show up in the shop page as well.

Just looking through my templates, the shop page (archive-product.php) is using the exact same calls to get the sidebar that the single product pages are using, and the widgets are displaying fine on those, so it doesn’t appear to be an issue with the template…

After further digging…

It seems the problem boils down to CAS not detecting that it is on the Shop page. I’ve played a bit with the template files and all the possible settings in CAS, disabled any plugins that might be relevant, and nothing’s changed.

Same problem here. This plugin is endorsed on the official WooCommerce site as the best solution to changing add to cart labels, so please address this in an update. The original post in this thread is almost 3 months old…

It works, thanks!

Just a heads up, both .rpscw-recentpostwrap and .rpscw-recentposts have a min-height of 220px. And the code does seem to generate some empty <p> tags or some empty space which WordPress wraps in <p> tags, which is contributing to extra height.

• This reply was modified 7 years, 2 months ago by luboslives.

Update – it’s actually happening on the same browser, not just the same machine. I brought in another user from a live site (id 1633), and I added something new to his wishlist in Firefox this time (the first test was done in Chrome). I saw that he had taken over the existing wishlist (id 1) which was created by my admin account while using Firefox. Then I logged out and logged in with user id 3 and now user 3 has taken ownership of that wishlist.

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