Paulo Arromba

Hello,
I audited the patch on a testing environment and concluded the patch is harmless. Furthermore the added code doesn’t seem to be used at all, and I found no vulnerability that would need further action from WooCommerce or Combell.

In the meantime, we internally checked the area that is supposedly being patched, and found no reasons for concern.

Are the webshops hosted on standoutmedia.dk?
I found this reference for that patch.
In the meantime, that method does not look malicious and does not directly overwrite any of the methods called in WooCommerce codebase.
I would recommend to contact your hosting provider to confirm this is actually legit.

Hi @shaprack, can you tell me which version of WooCommerce is running on your site?

I confirm this comment is not present on the WooCommerce codebase, and probably comes from another installed plugin. Maybe this one? Can you deactivate plugins one by one and check which one is responsible?

@smokingblends If you need further assistance in tweaking the provided info or styling the author box, feel free to tag me here.

Hi @smokingblends
Unfortunately, those guides are too generic, and it depends on the theme’s implementation of templates and templates part. In this case, Storefront uses a template part to display the post, and that is the reason the_content() is not present there.

Furthermore, editing the theme files is not a safe and future-proof option; each update would revert your changes. If you want to do many modifications, I would advise you to create a child theme. (sorry, just noticed you are already using a child theme)

For this specific situation, the safest way would be to use the storefront_single_post_bottom action, which will get fired after the post content (just like the post nav and comments).

I have rewriten the guide’s example to use this action instead (you can paste it at the end of your child theme functions.php file):

add_action('storefront_single_post_bottom', function() {
?>
<div class="about-author">
<div class="about-author-image">
<?php echo get_avatar(get_the_author_meta('ID'), 250); ?>
</div>
<div class="about-author-text">
<h3>About <?php echo get_the_author_meta( 'display_name'); ?></h3>
<?php echo wpautop(get_the_author_meta('description')); ?>
<a href="<?php echo get_author_posts_url(get_the_author_meta('ID')); ?>">View all posts by <?php the_author(); ?></a>
</div>
</div>
<style>/* insert custom css here */</style>
<?php
}, 1);

 

Please note, that it might need tweaking to look good. I left an indication where custom css to address styling could be added.

• This reply was modified 1 year, 1 month ago by Paulo Arromba.

Thank you so much for the steps @dangoodman, I was able to reproduce the bug and a fix was released on the latest update (10.9.2)

@dangoodman On that screen, edit the template, remove blocks and insert the shortcode block.
Also, ensure you have a cart and checkout page assigned https://imgur.com/a/36AUc6i

• This reply was modified 1 year, 3 months ago by Paulo Arromba.

Moreover, I can neither remove nor restore the new Cart and Checkout pages from Trash. Every time I click Delete Permanently, it redirects to the page edit page. The same happens when I click Restore.

@dangoodman if you have the Cart and Checkout pages trashed, try to restore them via bulk actions. That redirect is a known bug going to be addressed.

After you restore the pages, edit the templates for Cart and Checkout, and you can use the shortcode block to re-add the shortcode versions.

We are very sorry for the trouble caused, and working hard on polishing the feature based on these reports.

• This reply was modified 1 year, 3 months ago by Paulo Arromba.

Hi @dangoodman I’m currently investigating this issue, and currently everything points to be an issue installing WP+WC at the same time, introducing templates for Cart and Checkout, but not having the initial shortcode pages to migrate the content into the templates (default templates are block based).

Can you please provide steps you used for this, so I can test against a possible fix?

However, after installing WP + WC 8.0 (no other plugins) from scratch