Title: Problems with markup
Last modified: May 15, 2021

---

# Problems with markup

 *  Resolved [samflynn](https://wordpress.org/support/users/samflynn/)
 * (@samflynn)
 * [4 years, 12 months ago](https://wordpress.org/support/topic/problems-with-markup/)
 * Can it be a problem of a subsidiary? I moved markup after the latest updates.
   
   Updates were both on WooCommerce and on Blocksy [https://postimg.cc/Sj9TKTYF](https://postimg.cc/Sj9TKTYF)
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fproblems-with-markup%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 5 replies - 1 through 5 (of 5 total)

 *  anonymized-15227681
 * (@anonymized-15227681)
 * [4 years, 12 months ago](https://wordpress.org/support/topic/problems-with-markup/#post-14443023)
 * Hi [@samflynn](https://wordpress.org/support/users/samflynn/)
 * I’ve taken a look at your website and it seems that things are normal now. Sometimes,
   checkout plugins might interfere with a theme’s styling and want to dictate their
   own styling.
 * Let us know if the problem is still happening and we will gladly take a look 
   to see what’s going on.
 * Thanks
 *  Thread Starter [samflynn](https://wordpress.org/support/users/samflynn/)
 * (@samflynn)
 * [4 years, 12 months ago](https://wordpress.org/support/topic/problems-with-markup/#post-14443708)
 * Hello.
    To search for problems I used this HEALTH Check & Troubleshooting plugin
   I disconnected all the plugins and left only Woocoommerce enabled. The problem
   markup did not leave. I switched from a subsidiary to the parent adaptive markup
   recovered but partially. P.S. I do not think that the problem is in the subject,
   I just know that the technical support is a BlockSy responsive to help.
 *  anonymized-15227681
 * (@anonymized-15227681)
 * [4 years, 12 months ago](https://wordpress.org/support/topic/problems-with-markup/#post-14446681)
 * Hi [@samflynn](https://wordpress.org/support/users/samflynn/)
 * Could you please get back to us with more details on this? In your first screenshot,
   the WooCommerce logs span comes from a third party plugin that breaks the styling
   of the page.
 * Blocksy does not have anything related to WooCommerce logs.
 * I suggest you take a look at your third party plugins and see what might affect
   that cart selector.
 * Thanks
 *  Theme Author [Creative Themes](https://wordpress.org/support/users/creativethemeshq/)
 * (@creativethemeshq)
 * [4 years, 12 months ago](https://wordpress.org/support/topic/problems-with-markup/#post-14446931)
 * Hi [@samflynn](https://wordpress.org/support/users/samflynn/),
    As I can see 
   from your cart page code – you are using an old theme version.
 * Please try to update do the latest theme version this could help to solve your
   problem.
 *  Thread Starter [samflynn](https://wordpress.org/support/users/samflynn/)
 * (@samflynn)
 * [4 years, 12 months ago](https://wordpress.org/support/topic/problems-with-markup/#post-14454656)
 * I solved the problem of replacing the file:
    From – /public_html/wp-content/themes/
   blocksy/woocommerce/cart/cart.php. in – /public_html/wp-content/themes/blocksy-
   child/woocommerce/cart/cart.php.
    -  This reply was modified 4 years, 12 months ago by [samflynn](https://wordpress.org/support/users/samflynn/).

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Problems with markup’ is closed to new replies.

 * ![](https://i0.wp.com/themes.svn.wordpress.org/blocksy/2.1.41/screenshot.jpg)
 * Blocksy
 * [Support Threads](https://wordpress.org/support/theme/blocksy/)
 * [Active Topics](https://wordpress.org/support/theme/blocksy/active/)
 * [Unresolved Topics](https://wordpress.org/support/theme/blocksy/unresolved/)
 * [Reviews](https://wordpress.org/support/theme/blocksy/reviews/)

 * 5 replies
 * 3 participants
 * Last reply from: [samflynn](https://wordpress.org/support/users/samflynn/)
 * Last activity: [4 years, 12 months ago](https://wordpress.org/support/topic/problems-with-markup/#post-14454656)
 * Status: resolved