rebecca

Hi @zoonini – perhaps there is something I am misunderstanding about how the default padding (.has-global-padding) works and is declared in a theme? I still couldn’t get a standard paragraph block to line up exactly with the content inside a full width block that has padding applied. The left-right spacing didn’t match up even when I tried setting the padding values to be the same using the Inspector in my browser.

EDIT: I have just tried this again and you’re right, it’s now working as expected – strange! Thanks again for all your help.

• This reply was modified 1 year, 11 months ago by rebecca.
• This reply was modified 1 year, 11 months ago by rebecca.

Thank you so much @zoonini for taking the time to test and provide examples – this is really generous of you.

This has helped me find a solution that works for me, which is to place ALL content blocks inside full-width Group (or Cover) blocks and set the padding value in the editor, as you have described. The content which I mentioned as being ‘outside’ of a full width block can also be placed inside a full-width Group block; the only difference is that the Group block doesn’t have a background colour applied. If all content on the page or post is placed inside full-width group blocks (with the same left/right padding applied), the inner blocks line up as expected at all screen sizes.

This is the ‘obvious’ answer I have been searching for and hadn’t quite managed to put together, so I am really grateful.

Thank you again!

Hi @zoonini , thank you for taking the time to reply, and for your offer of further help. I really appreciate it.

I’m not really trying to achieve a different appearance on wider and smaller screens, so I’m not sure that a media query would be helpful. It’s more that, by default, content blocks outside of a full-width block (such as Group) behave differently from content blocks inside a full-width block, even when ‘Inner blocks use content width’ is toggled on.

At all screen sizes, content blocks outside of a full-width block, such as a standard paragraph block, have left/right padding applied by default (.has-global-padding in the CSS). However, for content blocks inside a full-width block, as the screen size shrinks, the inner content always stretches to the very left and right of the screen with no (or very little) padding, even when it has the .has-global-padding class applied. If you have text inside a full-width block with no padding, this causes readability issues on smaller screens. What I am trying to achieve is that inner content blocks have left/right padding that matches the .has-global-padding value, at all screen sizes.

Unfortunately, I don’t have a site or page to share as this is more of a ‘theoretical’ problem I am experiencing while building pages with the Block Editor, and I think it may apply to all sites. Since posting the topic I have found that the problem occurs in other themes, not just the Twenty Twenty Three theme.

I hope this explains the problem further, and I still really hope there is something simple I am misunderstanding.

Thank you very much again!

• This reply was modified 1 year, 11 months ago by rebecca.

Hi Hannah, thank you for your reply. We are reasonably sure that the problem isn’t with Square, and as we are not currently using WooCommerce premium extensions, we felt that the WooCommerce forums were the appropriate place to seek support.

To sum up the issues we’re experiencing, since replacing our previous live WordPress site with the ‘new’ live site:

• New (processing) orders are not appearing in the WooCommerce app’s Orders tab, or the ‘Your Store Today’ summary in the WordPress dashboard. They are appearing on the main Orders dashboard page (WooCommerce/Orders) and in the WooCommerce stats.
• Previous (completed) orders are also not appearing in the WooCommerce app – there are no records of orders showing at all.
• While the ‘new’ version of the site was in development, we made sales on the ‘old’ (live) site. Before publishing the ‘new’ site, we used WordPress’ import/export feature to ensure the orders, products, customers etc were up to date in the database. However, we have now noticed that the newer, imported orders no longer have a product attached to them. The ‘Product’ section is blank and the items subtotal reads ￡0.00. We are not sure if this is related the above, or a separate issue.

Thank you again for your response so far. The status report for our site is below:

### WordPress Environment ###

WordPress address (URL): https://corinneyoungtextiles.co.uk
Site address (URL): https://corinneyoungtextiles.co.uk
WC Version: 5.2.2
REST API Version: ? 5.2.2
WC Blocks Version: ? 4.7.2
Action Scheduler Version: ? 3.1.6
WC Admin Version: ? 2.1.5
Log Directory Writable: ?
WP Version: 5.7.1
WP Multisite: –
WP Memory Limit: ? 40 MB - We recommend setting memory to at least 64MB. See: Increasing memory allocated to PHP
WP Debug Mode: –
WP Cron: ?
Language: en_GB
External object cache: –

### Server Environment ###

Server Info: Apache
PHP Version: 7.3.27
PHP Post Max Size: 64 MB
PHP Time Limit: 50000
PHP Max Input Vars: 5000
cURL Version: 7.64.0
OpenSSL/1.1.1d

SUHOSIN Installed: –
MySQL Version: 5.7.32-log
Max Upload Size: 64 MB
Default Timezone is UTC: ?
fsockopen/cURL: ?
SoapClient: ?
DOMDocument: ?
GZip: ?
Multibyte String: ?
Remote Post: ?
Remote Get: ?

### Database ###

WC Database Version: 5.2.2
WC Database Prefix: wp1960_
Total Database Size: 30.13MB
Database Data Size: 22.97MB
Database Index Size: 7.16MB
wp1960_woocommerce_sessions: Data: 0.22MB + Index: 0.02MB + Engine InnoDB
wp1960_woocommerce_api_keys: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp1960_woocommerce_attribute_taxonomies: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp1960_woocommerce_downloadable_product_permissions: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wp1960_woocommerce_order_items: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp1960_woocommerce_order_itemmeta: Data: 0.14MB + Index: 0.16MB + Engine InnoDB
wp1960_woocommerce_tax_rates: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wp1960_woocommerce_tax_rate_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp1960_woocommerce_shipping_zones: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp1960_woocommerce_shipping_zone_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp1960_woocommerce_shipping_zone_methods: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp1960_woocommerce_payment_tokens: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp1960_woocommerce_payment_tokenmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp1960_woocommerce_log: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp1960_actionscheduler_actions: Data: 0.31MB + Index: 0.17MB + Engine InnoDB
wp1960_actionscheduler_claims: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp1960_actionscheduler_groups: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp1960_actionscheduler_logs: Data: 0.16MB + Index: 0.14MB + Engine InnoDB
wp1960_cli_cookie_scan: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp1960_cli_cookie_scan_categories: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp1960_cli_cookie_scan_cookies: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp1960_cli_cookie_scan_url: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp1960_cli_scripts: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp1960_commentmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp1960_comments: Data: 0.16MB + Index: 0.09MB + Engine InnoDB
wp1960_email_log: Data: 2.52MB + Index: 0.00MB + Engine InnoDB
wp1960_failed_jobs: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp1960_links: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp1960_mailchimp_carts: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp1960_mailchimp_jobs: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp1960_options: Data: 7.39MB + Index: 0.23MB + Engine InnoDB
wp1960_postmeta: Data: 6.52MB + Index: 4.03MB + Engine InnoDB
wp1960_posts: Data: 2.52MB + Index: 0.48MB + Engine InnoDB
wp1960_queue: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp1960_termmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp1960_terms: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp1960_term_relationships: Data: 0.06MB + Index: 0.02MB + Engine InnoDB
wp1960_term_taxonomy: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp1960_usermeta: Data: 0.11MB + Index: 0.06MB + Engine InnoDB
wp1960_users: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wp1960_wc_admin_notes: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp1960_wc_admin_note_actions: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp1960_wc_category_lookup: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp1960_wc_customer_lookup: Data: 0.05MB + Index: 0.03MB + Engine InnoDB
wp1960_wc_download_log: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp1960_wc_order_coupon_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp1960_wc_order_product_lookup: Data: 0.05MB + Index: 0.06MB + Engine InnoDB
wp1960_wc_order_stats: Data: 0.05MB + Index: 0.05MB + Engine InnoDB
wp1960_wc_order_tax_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp1960_wc_product_meta_lookup: Data: 0.02MB + Index: 0.09MB + Engine InnoDB
wp1960_wc_reserved_stock: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp1960_wc_tax_rate_classes: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp1960_wc_webhooks: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp1960_woocommerce_square_customers: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp1960_wpgdprc_consents: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp1960_wt_iew_action_history: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp1960_wt_iew_cron: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp1960_wt_iew_ftp: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp1960_wt_iew_mapping_template: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp1960_yoast_indexable: Data: 1.44MB + Index: 0.50MB + Engine InnoDB
wp1960_yoast_indexable_hierarchy: Data: 0.09MB + Index: 0.14MB + Engine InnoDB
wp1960_yoast_migrations: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp1960_yoast_primary_term: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp1960_yoast_seo_links: Data: 0.16MB + Index: 0.09MB + Engine InnoDB
wp1960_yoast_seo_meta: Data: 0.08MB + Index: 0.00MB + Engine InnoDB

### Post Type Counts ###

acf: 3
acf-field: 4
acf-field-group: 4
amn_smtp: 1
astra-advanced-hook: 6
attachment: 928
cookielawinfo: 6
custom_css: 1
customize_changeset: 76
elementor_library: 1
envira: 3
event: 1
exhibition: 26
feedback: 19
flamingo_contact: 144
flamingo_inbound: 170
foogallery: 1
jetpack_migration: 2
jetpack-portfolio: 1
mc4wp-form: 1
ml-slide: 15
ml-slider: 1
nav_menu_item: 20
oembed_cache: 23
page: 17
post: 1
press: 13
product: 127
product_variation: 2
revision: 424
shop_coupon: 4
shop_order: 171
shop_order_refund: 5
wpcf7_contact_form: 1

### Security ###

Secure connection (HTTPS): ?
Hide errors from visitors: ?

### Active Plugins (21) ###

ACF Content Analysis for Yoast SEO: by Thomas Kr?ftner
ViktorFroberg
marol87
pekz0r
angrycreative
Team Yoast – 3.0.1

Advanced Custom Fields: by Elliot Condon – 5.9.5
Akismet Anti-Spam: by Automattic – 4.1.9
Astra Pro: by Brainstorm Force – 3.3.2
Contact Form 7: by Takayuki Miyoshi – 5.4
CY Custom Pass: by  –
CY Exhibitions: by  –
CY Press: by  –
Flamingo: by Takayuki Miyoshi – 2.2.1
Jetpack by WordPress.com: by Automattic – 9.6.1
Mailchimp for WooCommerce: by Mailchimp – 2.5.1
MetaSlider: by MetaSlider – 3.20.3
Simple Lightbox: by Archetyped – 2.8.1
Ultimate Addons for Gutenberg: by Brainstorm Force – 1.22.2
Velvet Blues Update URLs: by VelvetBlues.com – 3.2.10
WooCommerce PayPal Checkout Gateway: by WooCommerce – 2.1.1
WooCommerce Square: by WooCommerce – 2.4.1
WooCommerce: by Automattic – 5.2.2
WordPress Importer: by wordpressdotorg – 0.7
Yoast SEO: by Team Yoast – 16.1.1
WP GDPR Compliance: by Van Ons – 1.5.6

### Inactive Plugins (1) ###

Really Simple SSL: by Really Simple Plugins – 4.0.14

### Settings ###

API Enabled: ?
Force SSL: ?
Currency: GBP (￡)
Currency Position: left
Thousand Separator: ,
Decimal Separator: .
Number of Decimals: 2
Taxonomies: Product Types: external (external)
grouped (grouped)
simple (simple)
variable (variable)

Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)
exclude-from-search (exclude-from-search)
featured (featured)
outofstock (outofstock)
rated-1 (rated-1)
rated-2 (rated-2)
rated-3 (rated-3)
rated-4 (rated-4)
rated-5 (rated-5)

Connected to WooCommerce.com: ?

### WC Pages ###

Shop base: #8 - /shop/
Basket: #9 - /basket/
Checkout: #10 - /checkout/
My account: #11 - /my-account/
Terms and conditions: ? Page not set

### Theme ###

Name: corinneyoungtextiles
Version: 1.0.0
Author URL: https://www.rebeccayoungdesign.co.uk
Child Theme: ?
Parent Theme Name: Astra
Parent Theme Version: 3.3.3
Parent Theme Author URL: https://wpastra.com/about/
WooCommerce Support: ?

### Templates ###

Overrides: corinneyoungtextiles/woocommerce/emails/customer-completed-order.php
corinneyoungtextiles/woocommerce/emails/customer-new-account.php
corinneyoungtextiles/woocommerce/emails/customer-processing-order.php
corinneyoungtextiles/woocommerce/emails/customer-refunded-order.php
corinneyoungtextiles/woocommerce/emails/customer-reset-password.php

### Square ###

Environment: Production
Tokenization Enabled: –
Debug Mode: Off

### Action Scheduler ###

Complete: 777
Oldest: 2021-03-24 13:05:23 +0000
Newest: 2021-04-24 10:43:44 +0100

Pending: 4
Oldest: 2021-04-24 11:43:44 +0100
Newest: 2021-04-26 13:05:54 +0100

### Status report information ###

Generated at: 2021-04-24 11:25:39 +01:00

• This reply was modified 3 years, 10 months ago by rebecca. Reason: formatting

Hi Jose, thank you so much for your reply. Unfortunately I don’t have another operating system to test it on, but have just attempted the WordPress 4.8 update in Firefox (I usually use Chrome) and am still having issues. This time the update page hangs on ‘Unpacking the update’, and the site is in maintenance mode (I’ll now remove the .maintenance file via FTP, of course).

The issue seems to affect all plugin updates.

Thank you again!

Hi there. I really do need help with this, please – I’m still receiving HTTP 500 error on the front end submission form, which I think is caused by a conflict with WP Super Cache. I also still seem to view ‘cached’ versions of some of site’s pages after WP Super Cache has been removed.

Please let me know if there is anything else I need to do, in addition to the above, to make sure every element of WP Super Cache is completely removed.

Thank you!

Thank you for taking the time to reply – I appreciate it!

I have done this and am still receiving the errors. However, I am now almost certain it’s the ‘leftover’ caching plugin that’s the problem. I think it was WP Super Cache. I thought I had removed it (including from htaccess and wp-config) – but when I tested with the Twenty Sixteen theme and changed back again, the Form Submission page was still showing in Twenty Sixteen (after refreshing with F5).

Should I contact the WP Super Cache support instead?

Thanks again!

• This reply was modified 7 years, 10 months ago by rebecca.

Realised shortly after posting how ridiculous the question is – can a moderator please delete this topic? Thank you!

Excellent – I had no idea it would be this simple, but removing the folder and reinstalling Events Manager has worked a treat.

Thank you so much again – I appreciate it!

Hi otaviof, thank you for taking the time to reply.

If I do this, will I be able to recover my previous Events Manager settings and event content?

Perfect – thank you!

Could the problem be anything to do with my website files being uploaded to public_html on the server (which is where I was told to put them)? Is that affecting the links somehow, e.g. to the font files in my child theme?

Hi Eric, thank you very much for taking the time to reply.

That does make sense and I think is probably true. However, I don’t have header.php in my child theme because I haven’t needed to alter it, so the issue isn’t there, unfortunately.

The icon font files meanwhile are in a folder called ‘fonts’ inside the child theme’s folder.

I have migrated other sites before and done things exactly the same way, so I don’t know what could be different this time!

Hi Fulvio,

Thank you. It turns out you’re absolutely right – after about the fifteenth time of checking and double-checking the settings, it’s my fault after all – it has been feeding from the wrong place since I changed the ID. It’s now corrected and working fine.

Thank you very much for all your help, and for the information about the update.

Hi,

I still need to resolve issue, with no events showing on the Google Calendar grid widget. Do you have any further advice?