Pedro

@grola It seems it’s working now. Maybe it was a cache issue but it’s strange i’m not using anything. Browser cache maybe…

Thanks anyway.

@grola Hi. Thanks for the quick reply.
Because I’m still in development, I’m not using any cache plugin. Not even in the server level. What could it be?

What do you mean to check if LFFS is enable on other methods?

Found the reason behind the error.

My host doesn’t allow the use of sending emails trough mail function and it need to be trough SMTP. The error was because i didn’t had any SMTP plugin configured in wordpress and my email notifications were giving this error.

Going to close the status of this post to Resolved

WordPress Environment

WordPress address (URL): https://atelier3b.com
Site address (URL): https://atelier3b.com
WC Version: 8.2.1
REST API Version: ? 8.2.1
WC Blocks Version: ? 11.1.2
Action Scheduler Version: ? 3.6.3
Log Directory Writable: ?
WP Version: 6.3.2
WP Multisite: –
WP Memory Limit: 512 MB
WP Debug Mode: –
WP Cron: ?
Language: pt_PT
External object cache: – Server Environment

Server Info: Apache
PHP Version: 8.1.24
PHP Post Max Size: 128 MB
PHP Time Limit: 30
PHP Max Input Vars: 1000
cURL Version: 7.87.0
OpenSSL/1.1.1w

SUHOSIN Installed: –
MySQL Version: 8.0.35
Max Upload Size: 128 MB
Default Timezone is UTC: ?
fsockopen/cURL: ?
SoapClient: ?
DOMDocument: ?
GZip: ?
Multibyte String: ?
Remote Post: ?
Remote Get: ? Database

WC Database Version: 8.2.1
WC Database Prefix: wp_
Tamanho total da base de dados: 25.24MB
Tamanho dos dados da base de dados: 22.00MB
Tamanho do índice da base de dados: 3.24MB
wp_woocommerce_sessions: Dados: 0.02MB + índice: 0.02MB + Engine InnoDB
wp_woocommerce_api_keys: Dados: 0.02MB + índice: 0.03MB + Engine InnoDB
wp_woocommerce_attribute_taxonomies: Dados: 0.02MB + índice: 0.02MB + Engine InnoDB
wp_woocommerce_downloadable_product_permissions: Dados: 0.02MB + índice: 0.06MB + Engine InnoDB
wp_woocommerce_order_items: Dados: 0.02MB + índice: 0.02MB + Engine InnoDB
wp_woocommerce_order_itemmeta: Dados: 0.08MB + índice: 0.06MB + Engine InnoDB
wp_woocommerce_tax_rates: Dados: 0.02MB + índice: 0.06MB + Engine InnoDB
wp_woocommerce_tax_rate_locations: Dados: 0.02MB + índice: 0.03MB + Engine InnoDB
wp_woocommerce_shipping_zones: Dados: 0.02MB + índice: 0.00MB + Engine InnoDB
wp_woocommerce_shipping_zone_locations: Dados: 0.02MB + índice: 0.03MB + Engine InnoDB
wp_woocommerce_shipping_zone_methods: Dados: 0.02MB + índice: 0.00MB + Engine InnoDB
wp_woocommerce_payment_tokens: Dados: 0.02MB + índice: 0.02MB + Engine InnoDB
wp_woocommerce_payment_tokenmeta: Dados: 0.02MB + índice: 0.03MB + Engine InnoDB
wp_woocommerce_log: Dados: 0.02MB + índice: 0.02MB + Engine InnoDB
wp_actionscheduler_actions: Dados: 0.11MB + índice: 0.11MB + Engine InnoDB
wp_actionscheduler_claims: Dados: 0.02MB + índice: 0.02MB + Engine InnoDB
wp_actionscheduler_groups: Dados: 0.02MB + índice: 0.02MB + Engine InnoDB
wp_actionscheduler_logs: Dados: 0.09MB + índice: 0.09MB + Engine InnoDB
wp_btcbi_flow: Dados: 0.02MB + índice: 0.00MB + Engine InnoDB
wp_btcbi_log: Dados: 0.02MB + índice: 0.02MB + Engine InnoDB
wp_cmplz_cookiebanners: Dados: 0.02MB + índice: 0.00MB + Engine InnoDB
wp_cmplz_cookies: Dados: 0.02MB + índice: 0.00MB + Engine InnoDB
wp_cmplz_services: Dados: 0.02MB + índice: 0.00MB + Engine InnoDB
wp_commentmeta: Dados: 0.02MB + índice: 0.03MB + Engine InnoDB
wp_comments: Dados: 0.02MB + índice: 0.09MB + Engine InnoDB
wp_duplicator_pro_entities: Dados: 0.02MB + índice: 0.02MB + Engine InnoDB
wp_duplicator_pro_packages: Dados: 0.02MB + índice: 0.02MB + Engine InnoDB
wp_e_events: Dados: 0.02MB + índice: 0.02MB + Engine InnoDB
wp_e_submissions: Dados: 0.02MB + índice: 0.27MB + Engine InnoDB
wp_e_submissions_actions_log: Dados: 0.02MB + índice: 0.11MB + Engine InnoDB
wp_e_submissions_values: Dados: 0.02MB + índice: 0.03MB + Engine InnoDB
wp_frmt_form_entry: Dados: 0.02MB + índice: 0.05MB + Engine InnoDB
wp_frmt_form_entry_meta: Dados: 0.02MB + índice: 0.05MB + Engine InnoDB
wp_frmt_form_reports: Dados: 0.02MB + índice: 0.00MB + Engine InnoDB
wp_frmt_form_views: Dados: 0.02MB + índice: 0.06MB + Engine InnoDB
wp_links: Dados: 0.02MB + índice: 0.02MB + Engine InnoDB
wp_options: Dados: 6.41MB + índice: 0.08MB + Engine InnoDB
wp_postmeta: Dados: 10.23MB + índice: 0.52MB + Engine InnoDB
wp_posts: Dados: 3.45MB + índice: 0.16MB + Engine InnoDB
wp_rank_math_404_logs: Dados: 0.02MB + índice: 0.02MB + Engine InnoDB
wp_rank_math_internal_links: Dados: 0.02MB + índice: 0.02MB + Engine InnoDB
wp_rank_math_internal_meta: Dados: 0.02MB + índice: 0.00MB + Engine InnoDB
wp_rank_math_redirections: Dados: 0.02MB + índice: 0.02MB + Engine InnoDB
wp_rank_math_redirections_cache: Dados: 0.02MB + índice: 0.02MB + Engine InnoDB
wp_shopmagic_automation_outcome: Dados: 0.02MB + índice: 0.00MB + Engine InnoDB
wp_shopmagic_automation_outcome_logs: Dados: 0.14MB + índice: 0.02MB + Engine InnoDB
wp_shopmagic_guest: Dados: 0.02MB + índice: 0.00MB + Engine InnoDB
wp_shopmagic_guest_meta: Dados: 0.02MB + índice: 0.02MB + Engine InnoDB
wp_shopmagic_marketing_lists: Dados: 0.02MB + índice: 0.00MB + Engine InnoDB
wp_shopmagic_optin_email: Dados: 0.02MB + índice: 0.00MB + Engine InnoDB
wp_shopmagic_tracked_emails: Dados: 0.02MB + índice: 0.05MB + Engine InnoDB
wp_shopmagic_tracked_emails_clicks: Dados: 0.02MB + índice: 0.02MB + Engine InnoDB
wp_term_relationships: Dados: 0.02MB + índice: 0.02MB + Engine InnoDB
wp_term_taxonomy: Dados: 0.02MB + índice: 0.03MB + Engine InnoDB
wp_termmeta: Dados: 0.02MB + índice: 0.03MB + Engine InnoDB
wp_terms: Dados: 0.02MB + índice: 0.03MB + Engine InnoDB
wp_usermeta: Dados: 0.02MB + índice: 0.03MB + Engine InnoDB
wp_users: Dados: 0.02MB + índice: 0.05MB + Engine InnoDB
wp_wc_admin_note_actions: Dados: 0.05MB + índice: 0.02MB + Engine InnoDB
wp_wc_admin_notes: Dados: 0.06MB + índice: 0.00MB + Engine InnoDB
wp_wc_category_lookup: Dados: 0.02MB + índice: 0.00MB + Engine InnoDB
wp_wc_customer_lookup: Dados: 0.02MB + índice: 0.03MB + Engine InnoDB
wp_wc_download_log: Dados: 0.02MB + índice: 0.03MB + Engine InnoDB
wp_wc_order_addresses: Dados: 0.02MB + índice: 0.06MB + Engine InnoDB
wp_wc_order_coupon_lookup: Dados: 0.02MB + índice: 0.03MB + Engine InnoDB
wp_wc_order_operational_data: Dados: 0.02MB + índice: 0.03MB + Engine InnoDB
wp_wc_order_product_lookup: Dados: 0.02MB + índice: 0.06MB + Engine InnoDB
wp_wc_order_stats: Dados: 0.02MB + índice: 0.05MB + Engine InnoDB
wp_wc_order_tax_lookup: Dados: 0.02MB + índice: 0.03MB + Engine InnoDB
wp_wc_orders: Dados: 0.02MB + índice: 0.11MB + Engine InnoDB
wp_wc_orders_meta: Dados: 0.02MB + índice: 0.03MB + Engine InnoDB
wp_wc_product_attributes_lookup: Dados: 0.02MB + índice: 0.02MB + Engine InnoDB
wp_wc_product_download_directories: Dados: 0.02MB + índice: 0.02MB + Engine InnoDB
wp_wc_product_meta_lookup: Dados: 0.02MB + índice: 0.09MB + Engine InnoDB
wp_wc_rate_limits: Dados: 0.02MB + índice: 0.02MB + Engine InnoDB
wp_wc_reserved_stock: Dados: 0.02MB + índice: 0.00MB + Engine InnoDB
wp_wc_tax_rate_classes: Dados: 0.02MB + índice: 0.02MB + Engine InnoDB
wp_wc_webhooks: Dados: 0.02MB + índice: 0.02MB + Engine InnoDB Post Type Counts

attachment: 37
elementor_font: 1
elementor_icons: 2
elementor_library: 7
forminator_forms: 1
giftcard: 4
nav_menu_item: 4
page: 17
post: 3
product: 7
product_variation: 21
revision: 411
shop_coupon: 2
shop_order: 43
shopmagic_automation: 2
shopmagic_list: 1
wpcode: 18
yaymail_template: 11 Security

Secure connection (HTTPS): ?
Hide errors from visitors: ? Active Plugins (1)

WooCommerce: por Automattic – 8.2.1 Inactive Plugins (23)

Complianz | GDPR/CCPA Cookie Consent: por Really Simple Plugins – 6.5.5
Customizer for WooCommerce: por SkyVerge – 2.8.0
Elementor: por Elementor.com – 3.17.1
Elementor Pro: por Elementor.com – 3.17.0
Envato Elements: por Envato – 2.0.12
EU/UK VAT Compliance for WooCommerce (Free): por David Anderson – 1.28.0
Fake Pay For WooCommerce: por Anthony Graddy – 1.1.0
Filester - File Manager Pro: por Ninja Team – 1.8.1
Folders: por Premio – 2.9.8
Forminator: por WPMU DEV – 1.27.0
Health Check & Troubleshooting: por The www.remarpro.com community – 1.7.0
Loco Translate: por Tim Whitlock – 2.6.6
Multibanco, MB WAY, Credit card and Payshop (IfthenPay) for WooCommerce: por PT Woo Plugins (by Webdados) – 8.6.0
NIF (Num. de Contribuinte Português) for WooCommerce: por PT Woo Plugins (by Webdados) – 5.4
PhastPress: por Albert Peschar – 2.18
Rank Math SEO: por Rank Math – 1.0.204
ShopMagic for WooCommerce: por WP Desk – 4.2.1
Ultimate Gift Cards For WooCommerce: por WP Swings – 2.6.1
Variation Swatches for WooCommerce: por Emran Ahmed – 2.0.28
WooCommerce Payments: por Automattic – 6.6.2
WPCode Lite: por WPCode – 2.1.4.1
WP Meteor: por Aleksandr Guidrevitch – 3.3.1
YayMail - WooCommerce Email Customizer: por YayCommerce – 3.3.8 Settings

API Enabled: –
Force SSL: –
Currency: EUR (€)
Currency Position: right_space
Thousand Separator: ,
Decimal Separator: .
Number of Decimals: 2
Taxonomies: Product Types: external (external)
grouped (grouped)
simple (simple)
variable (variable)
wgm_gift_card (wgm_gift_card)

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: –
Enforce Approved Product Download Directories: ?
HPOS feature screen enabled: –
HPOS feature enabled: –
Order datastore: WC_Order_Data_Store_CPT
HPOS data sync enabled: – WC Pages

Página da Loja: #7 - /loja/
Carrinho: #8 - /carrinho/
Finalizar compras: #9 - /checkout/
A minha conta: #10 - /my-account/
Termos e condi??es: ? Página n?o definida Theme

Name: Storefront
Version: 4.5.3
Author URL: https://woocommerce.com/
Child Theme: ? – Se estiver a modificar o tema do WooCommerce ou um tema principal que n?o construiu pessoalmente
recomendamos o uso de um tema dependente. Veja: Como criar um tema dependente

WooCommerce Support: ? Templates

Overrides: – Admin

Enabled Features: activity-panels
analytics
product-block-editor
coupons
core-profiler
customer-effort-score-tracks
import-products-task
experimental-fashion-sample-products
shipping-smart-defaults
shipping-setting-tour
homescreen
marketing
mobile-app-banner
navigation
onboarding
onboarding-tasks
product-variation-management
remote-inbox-notifications
remote-free-extensions
payment-gateway-suggestions
shipping-label-banner
subscriptions
store-alerts
transient-notices
woo-mobile-welcome
wc-pay-promotion
wc-pay-welcome-page

Disabled Features: customize-store
minified-js
new-product-management-experience
settings
async-product-editor-category-field

Daily Cron: ? Next scheduled: 2023-10-26 14:50:30 +00:00
Options: ?
Notes: 69
Onboarding: skipped Action Scheduler

Concluída: 256
Oldest: 2023-09-30 14:51:34 +0000
Newest: 2023-10-25 13:39:46 +0000

Pendente: 45
Oldest: 2023-10-26 13:39:46 +0000
Newest: 2023-10-27 17:47:56 +0000

Falhada: 22
Oldest: 2023-10-11 10:42:18 +0000
Newest: 2023-10-24 16:52:57 +0000 Status report information

Generated at: 2023-10-27 17:49:57

After some searching i found some ideas that from migrating from local server to a live host it could change the auto-increment values on the Woocommerce tables and that can cause some issues, thus the error.

So at this moment i manage to troubleshoot the following:

Already tried to verify the tables using the Woocommerce Tools but that didn’t fixed the issue.

At the moment I have only Woocommerce plugin and Storefront theme enable. When I place an order in the front-end, I see the error “We were unable to process your order, please try again” and the order is created in the back-end.

In Woocommerce Status -> Logs: There is no fatal errors showing.

Anyone with ideas of how i can fix this or even troubleshoot this issue?
About the auto-increment can someone post here a way of checking the tables for that information and fix it. I imagine it should be done on phpmyadmin.

I will post my System report in the next comment.

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

Dear GravityWP team,

That worked perfectly. Many Thanks.

Dear Support team,

Is this issue fixed? I have v2.4.2 and still is happening.

Got it…..

It’s not perfect because I lost the effect of the white box that wraps the menu, but it works ok.

the element that i used to make it transparent was:

.ast-builder-menu-1 .main-header-menu, .ast-builder-menu-1 .main-header-menu .sub-menu

If you have any idea why only happens in the event list page let me know ??

UPDATE: I found the reason why the header was not transparent in this page….I had an option enable to disable transparent header on 404, search and archive pages….I disable that and now it works perfectly.

Thanks for all the help,

Pedro

• This reply was modified 2 years, 8 months ago by Pedro.

@jaimemarchwinski The black section of the title that i mentioned before i managed to put it transparent with the element:

.tribe-events-calendar-list__event

Now to make it perfect i just need for the menu to be as it is on the rest of the webpage.

Pedro

• This reply was modified 2 years, 8 months ago by Pedro.
• This reply was modified 2 years, 8 months ago by Pedro.

Once again @jaimemarchwinski Thanks <3

It helped a little, yes….

The section of the menu, stayed black, it doesn’t go into transparent mode…I wonder why?
Also the area of the title as a black rectangle that doesn’t stay transparent. Is this because of the v2 views in the plugin? Because the single page event that still uses the legacy version of the plugin works well with this CSS code.

I’m going to do more testing and messing around to see if I can make it transparent.

If you have more ideas please share.

Thanks,
Pedro

Thanks @jaimemarchwinski, I didn’t thought about that….wanted to go the difficult way instead the easy way ??

So, the CSS worked but now I have a different question.

I added a background image that display in the container and doesn’t change the header or the footer. We can see it working here: /eventos/

But if you go to the single event page (/evento/vivo/), the background image does overlap the header, and because the header is set as transparent it really looks good, as I wanted. But, I don’t really know how to do that in the all events page.

I tried using the .ast-container (not the .ast-separate-container) element but it doesn’t work well because some parts they stay black, not transparent.

Ideas?

Thanks,
Pedro

Thanks for the reply,

I still didn’t figure it out to do it.

I tried to use this cod to see if at least showed a different logo from the default one:

body:not(.home) .header_mid_inner .logo {
    background-image: url('/public_html/wp-content/themes/dance-studio/css/ASSOCADDDL_LOGO_P.png');
    background-repeat: no-repeat;
    background-size: 100%;
    display: block;
    position: relative;
    height: 85px;
    width: 180px;
}
body:not(.home) .header_mid_inner .logo img {
    display: none;
}

First I tried to add this code to the style.css but without any results. After I tried adding this code in the Additional CSS option in the Appearance Settings. For some reason if i use body:not(.home) it doesn’t work but if i use only .home the rule already works, at least to hide the default logo.

• This reply was modified 3 years, 1 month ago by Pedro.