-
Search Results
-
In reply to: Custom CSS not working
Hello together,
Actually I have experiences the same issue. On all elements through out the Avia Layout builder the custom css fields do not work no matter what I do. I need different sized buttons on all pages but I am not able to do that. It might be a problem for a lot more people I assume:(
Best,
AlxeanderWhen I or customers go to select their state from the dropdown during checkout in WooCommerce the state name will change to a different state name when they hover over it. For example if you hover over Iowa to select it it will disappear and change to Kansas. This makes it impossible to select the correct state. This issue also occurs in mobile.
I am running the current version of WP, Woo and also Jetpak using WooServices. I have deactivated all the plugins other than WooCommerce and the issue persists. I am not sure if this is an Enfold issue or something else. I looked at the source through Inspector and see that it’s different for the state dropdown fields than in your Enfold eCommerce demos. In our install the dropdown fields are in a list format ( ul > li ) while yours are in spans. Not sure why they are different.
What would cause the state to change and how can I keep it from happening?
In reply to: Mobile Phone Credit Card Area
Hi Jon,
We can’t target the font size of those fields with CSS, since they are added as iframes. We can target everything outside of the fields though, but I’m not sure exactly what you would like to reduce or remove. Please try to specify that a bit further so that we can give you some custom CSS to use.
Best regards,
RikardIn reply to: ACF Shortcode in Portfolio Ajax Preview
1) Adding a shortcode [av_video] in the editor of the Ajax Preview area. The video doesn’t appear in the frontend.
2) Adding a shortcode [acf field=””] of the Advanced Custom Fields Plugin in the editor of the Ajax Preview area. The content of the costum field doesn’t appear in the frontend.In reply to: Advanced Custom Fields display
Hi,
All my post contains custom fields that do not display in the enfold theme
The custom fields have to be added manually in the template. They will not be included in the default content automatically. If you are using the ACF plugin, you could use the get_field function, but if not use the get_post_meta function instead to fetch the value of the a custom field and render it in a template. For the post, you have to modify the single.php file or the includes > loop-index.php file.
// https://www.advancedcustomfields.com/resources/get_field/
// https://developer.wordpress.org/reference/functions/get_post_meta/If you search for a region in this page you will see the post displayed empty
Unfortunately, we do not provide support for third party plugins as stated on our support policy. Please contact the plugin developers for additional assistance regarding the filter plugin.
Thank you for your understanding.
Best regards,
IsmaelIn reply to: Advanced Custom Fields display
If you search for a region in this page you will see the post displayed empty
https://secure-it-pro.com/roseph_new/?page_id=37
All my post contains custom fields that do not display in the enfold theme
Screenshot of post are available here
https://1drv.ms/u/s!Alxw3yp_y0w-ka1vHHNW04jkPKBwWA?e=J3XYhDTopic: Error while saving.
As we know, Enfold Theme handles the new vs. old editor using its own setting. WIth the latest Enfold update, suddenly when using the classic editor the custom fields in The Events Calendar posts wouldn’t save. (This did not seem to be an issue when using the new block editor). Saving the post reset the custom fields, and an error message occurred in the message line under the post text input box: “Error while saving.” As I used the process of elimination, here is what I found:
– The issue was not actually confined to the events posts – the same issue existed with all posts, except that most posts don’t have custom fields so it went unnoticed at first. The issue may have gone undetected for several weeks.
– I consulted with SiteGround on the problem and they assigned a senior technician, who was unable to resolve the issue within the scope of the support they provide. They eliminated server/hosting configurations as a cause.
– I created a staging site to test the issue further by deactivating ALL plugins on the site. The issue continued with ALL plugins deactivated, so I concluded that the issue isn’t related to The Events Calendar, LearnDash, WooCommerce etc.
– Next I tested the Child Theme (child of the Enfold Theme) to see if the customization of the Child Theme might be the cause. However, the same issue existed when the bare Theme was used – so the customizations are not the issue.
– Next I changed the Theme to a standard WP Theme (2020 Theme) and found that the issue does NOT occur when the Enfold Theme is replaced by a different Theme.
– My conclusion is that the problem is the Enfold Theme, maybe connected to its own “classic editor” option built in.
– Finally – I have found a work around for the time being. Installing and activating the “Classic Editor” plugin (from WordPress) seems to override the themes version of the classic editor and allows saving posts. However, the error message still appears under the post content box, even though the posts seems to save OK.Is this a known problem the the latest release when using the classic editor with posts with customs fields (like Events Calendar)?
In reply to: Advanced Custom Fields display
Hi,
Thank you for the update.
Which part of the repertoire-des-membres page are the custom fields? Please post a screenshot using imgur or dropbox so that we can better understand what you did in the previous template.
Where and how did you place the custom fields previously?
Best regards,
IsmaelHi there!
The shortcode [acf field=””] of the Advanced Custom Fields Plugin doesn’t work in the preview text field of the ajax portfolio.
Do you have an idea?
Thanks
BerndIn reply to: WooCommerce Cart and Checkout Page
Hey npmcgrew,
Well, you need to customize WooCommerce pages. Here is how you can do it:
If you need further assistance please let us know.
Best regards,
VictoriaIn reply to: Advanced Custom Fields display
It runs fine on the site not using (roseph.ca) but I cannot get it to run on my site which is using Enfold (https://secure-it-pro.com/roseph_new/ ) even though I have iported the pages from the other site. I have attempted to edit the single.php file. It will then display the custom fields but not correctly
I am trying to display a custom field of “Subtitle” on my posts, but I can’t get them to display. I’ve tried using the ACF plugin as well as the built in custom field in the block editor as detailed < https://themeisle.com/blog/custom-fields-in-wordpress/ >, but I can’t get the single post or the archive loop to display the custom field.
I need to edit the loop-index.php file to add a subtitle after the title and before the categories, correct? If so, where in that file should I be adding the custom field call?
HI there,
I made a contact form according to my needs and it has a lot of fields. I receive emails from it, but do not receive the autoresponder.
Then I checked the case by using the default contact form, where I only changed the labels – all worked well.
I assume the size of my custom form prevents the autoresponder to be sent.I also checked some online resources:
#https://kriesi.at/documentation/enfold/contact-form/#my-contact-form-is-not-sending-emails-
#https://kriesi.at/support/topic/contact-form-not-sending-emails-9/
#https://kriesi.at/support/topic/mail-sent-from-contact-form-does-not-arrive/Please, advise me how to fix it.
Regards,
AleksandraHi, I am having problems displaying the advanced custom fields with the Enfold Theme. I can get them to display but they do not display correctly
Here is the website from which they are imported and how they display. We installed the same version of ACF Pro and Search and filter Pro
Here is what I see :
https://secure-it-pro.com/roseph_new/?p=677&preview_id=677&preview_nonce=0e39bcd4e8&preview=trueHi Rikard,
I have just had a look and the behavior appears to have changed, which is weird.
Now, as a user, I can edit the custom fields when clicking Edit Profile while Enfold is enabled – before they weren’t showing up at all on Enfold, only the text box at the top. Changes now save when clicking Update Profile or the checkbox, but the completed fields don’t show up on profile (View Profile) when Enfold is enabled. When Enfold Child is enabled, the custom fields don’t show up when clicking Edit Profile, or View Profile.
I have reached out to Ultimate Member and they’re insisting that it’s a theme (Enfold) conflict. I found this thread on WP support, I could be way off, but maybe this helps narrow it down? https://wordpress.org/support/topic/ultimate-member-2-1-6-theme-menus-breaking-changes/
In reply to: send button in one line with other buttons
Hey rixi,
Sorry for the late reply, and thanks for the link. As I understand your question you are referring to this form:
and you would like it to look like this:
you can do this within the form options, for each element go to the styling tab and choose the width you wish, for example 4 elements would fit in one line if each was 1/4 wide.
Another option would be to try this code in the General Styling > Quick CSS field or in the WordPress > Customize > Additional CSS field:.avia_ajax_form .form_element_half { width: 24% !important; } .avia_ajax_form .first_form { width: 24% !important; clear: right !important; } #av_section_2 > div > div > div > div > div > form > fieldset > p:nth-child(6) { width: 24% !important; clear: right !important; }This is what I used to take the screenshot above.
After applying the css, please clear your browser cache and check.Best regards,
MikeHello Enfold Support Team,
This is a two part question :
I have a custom post type named “Journal” . This custome post type has a custom field with slug “wpcf-field_link_url” which has an external url(each post has different url)
Part 1:
when I go to the archive page for this custom post type (arhive-journal.php – same as archive.php no customizations done), I am shown all the posts related to this post type.
When I click on “Read More” or the “title” , it navigates me to that Custom Post’s single page view i.e. by default we get taken to the Custom Post (single-journal.php which has same code as single.php – no customizations yet).Question 1:
How do I change the Link to point to the custom field “wpcf-filed_link_url” when clicked on “read more” and “title” instead of the self linkPart 2:
When i go to the single page view of the custom post type , (single-journal.php which has same code as single.php -no customizations yet) i am shown the feature image , title, description etc.
The featured image and title are links which point to the same page.Question 2:
How do I change the link for the title and image in Single custom post view to use the url defined in custom field “wpcf-filed_link_url” i.e. when Title or Image is clicked in the Single post view, it needs to open the link defined in custom field “wpcf-filed_link_url”NOTE: I have use toolset plugin to create custom posts and custom fields and manually created the single-journal.php , but could create the Display i wanted. On reading many forums i realized that Enfold theme is not compatible with toolset plugin. so i am not able to create a view from front end and now i am trying to make changes in template files directly.
In reply to: Integrating toolset
Hi,
This sounds like the same overall issue, the custom post type doesn’t show “the_content” on the front end, a filter would be needed, or the theme files would need to be adjusted, as in the case with Toolset.
To test try checking if your content shows on a “page”, were “the_content” is used, not a “post” or a “custom post type”, if this works then it would show that it is an issue with “the_content”.
For this issue the dev team writes:
The Custom Posts uses “WP_Hook::apply_filters” so a filter such as:$additional_info = array( ...... ) $content = apply_filters( 'avf_the_content', $content; $context, $additional_info );$context helps to figure out what location and with $additional_info you can render needed additional data.
Have a look at enfold\config-templatebuilder\avia-template-builder\php\shortcode-template.class.php shortcode_handler_prepare() and enfold\template-builder.php.Since you are not using Toolset now please see this thread, but I didn’t find much info on ACF & Custom Post Types UI, most threads point to ACF documentation, but I assume you are fimaular with this.
While I was researching this I found that the dev team has a new proposal for the Toolset team for “the_content”, Toolset has not replied yet, but I will post here:
If we add at the beginning of loop-index.php (line 8):if( false !== apply_filters( 'avf_replace_content', false, 'includes/loop-index' ) ) { return; }With this filter it is possible to replace content (not sidebar and header).
Best regards,
MikeHi there,
I need some assistance with an issue with the Ultimate Member plugin on one of our sites that appears to be caused by Enfold. They used to work fine together so I am not sure if this is related to a recent update.
First of all, we received an email from a user saying that when they edited their profile it wouldn’t save, but upon investigating, we found that the user page is no longer showing all the custom fields that it should.
It’s definitely caused by Enfold, because when I enable the Twenty Nineteen Theme only it works as expected and shows all custom fields. Also, when Enfold is enabled, clicking the checkmark to save the edits in the one text box that’s showing just reloads the edit page.
For speed, I have already created user access on the staging site for your team to take a look, details are in the private content box.
In reply to: Integrating toolset
Hi Mike
I steered in a completely different direction.
I installed Custom Post Types UI, created a ‘Paarden’ post type. So far so good. Then I need custom fields like age, gender, name, level, … etc. So I installed ACF, and made a group of fields for the post type Paarden. I set the field group to display on the custom post type ‘Paarden’, and they appear like they should. I also added this code https://kriesi.at/documentation/enfold/intro-to-layout-builder/#alb-for-any-post-type to be able to edit the custom post type Paarden with the Avia Layout Builder.BUT
Now I want to display the values of the ACF fields on the front-end of a Paarden-post. But that doesn’t work. The shortcodes in the ACF documentation don’t work for me, not in the classic editor and also not in de ALB. Also – I added an image element with the ALB in the custom post type, but that also doesn’t appear. Did I do something wrong with the ALB code? Why is nothing showing on the front-end? Please check the private section for links. Help :)
I don’t know how to clean that page from this code.
I have disabled and removed Visual composer.
I don’t have woocommerce files on Enfold Child.### WordPress Environment ###
WordPress address (URL): https://outlet.florens.it
Site address (URL): https://outlet.florens.it
WC Version: 4.4.1
REST API Version: ✔ 1.0.15
WC Blocks Version: ✔ 3.1.0
Action Scheduler Version: ✔ 3.1.6
WC Admin Version: ✔ 1.4.0
Log Directory Writable: ✔
WP Version: 5.5
WP Multisite: –
WP Memory Limit: 768 MB
WP Debug Mode: –
WP Cron: ✔
Language: it_IT
External object cache: –### Server Environment ###
Server Info: Apache
PHP Version: 7.3.20
PHP Post Max Size: 128 MB
PHP Time Limit: 120
PHP Max Input Vars: 3000
cURL Version: 7.66.0
OpenSSL/1.1.1g-fipsSUHOSIN Installed: –
MySQL Version: 5.7.26-29-log
Max Upload Size: 128 MB
Default Timezone is UTC: ✔
fsockopen/cURL: ✔
SoapClient: ✔
DOMDocument: ✔
GZip: ✔
Multibyte String: ✔
Remote Post: ✔
Remote Get: ✔### Database ###
WC Database Version: 4.3.3
WC Database Prefix: vmktf_
Dimensione totale database: 93.65MB
Dimensione dati database: 69.08MB
Dimensione indice database: 24.57MB
vmktf_woocommerce_sessions: Dati: 0.03MB + indice: 0.02MB + motore InnoDB
vmktf_woocommerce_api_keys: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
vmktf_woocommerce_attribute_taxonomies: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_woocommerce_downloadable_product_permissions: Dati: 0.02MB + indice: 0.06MB + motore InnoDB
vmktf_woocommerce_order_items: Dati: 0.09MB + indice: 0.05MB + motore InnoDB
vmktf_woocommerce_order_itemmeta: Dati: 1.52MB + indice: 0.42MB + motore InnoDB
vmktf_woocommerce_tax_rates: Dati: 0.02MB + indice: 0.06MB + motore InnoDB
vmktf_woocommerce_tax_rate_locations: Dati: 0.02MB + indice: 0.05MB + motore InnoDB
vmktf_woocommerce_shipping_zones: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_woocommerce_shipping_zone_locations: Dati: 0.02MB + indice: 0.05MB + motore InnoDB
vmktf_woocommerce_shipping_zone_methods: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_woocommerce_payment_tokens: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_woocommerce_payment_tokenmeta: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
vmktf_woocommerce_log: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_actionscheduler_actions: Dati: 0.02MB + indice: 0.11MB + motore InnoDB
vmktf_actionscheduler_claims: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_actionscheduler_groups: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_actionscheduler_logs: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
vmktf_adtribes_my_conversions: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_blogmeta: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
vmktf_blogs: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
vmktf_commentmeta: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
vmktf_comments: Dati: 0.28MB + indice: 0.30MB + motore InnoDB
vmktf_ewwwio_images: Dati: 0.01MB + indice: 0.01MB + motore MyISAM
vmktf_ewwwio_queue: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_hustle_modules: Dati: 0.00MB + indice: 0.00MB + motore MyISAM
vmktf_hustle_modules_meta: Dati: 0.00MB + indice: 0.01MB + motore MyISAM
vmktf_icl_content_status: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_icl_core_status: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_icl_flags: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_icl_languages: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
vmktf_icl_languages_translations: Dati: 0.20MB + indice: 0.14MB + motore InnoDB
vmktf_icl_locale_map: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_icl_message_status: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
vmktf_icl_mo_files_domains: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_icl_node: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_icl_reminders: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_icl_strings: Dati: 4.52MB + indice: 7.23MB + motore InnoDB
vmktf_icl_string_packages: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_icl_string_pages: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_icl_string_positions: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_icl_string_status: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_icl_string_translations: Dati: 5.52MB + indice: 2.52MB + motore InnoDB
vmktf_icl_string_urls: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_icl_translate: Dati: 1.52MB + indice: 0.05MB + motore InnoDB
vmktf_icl_translate_job: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_icl_translations: Dati: 0.45MB + indice: 1.17MB + motore InnoDB
vmktf_icl_translation_batches: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_icl_translation_status: Dati: 1.52MB + indice: 0.05MB + motore InnoDB
vmktf_layerslider: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_layerslider_revisions: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_links: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_newsletter: Dati: 0.25MB + indice: 0.09MB + motore InnoDB
vmktf_newsletter_emails: Dati: 1.52MB + indice: 0.00MB + motore InnoDB
vmktf_newsletter_sent: Dati: 1.52MB + indice: 0.66MB + motore InnoDB
vmktf_newsletter_stats: Dati: 1.52MB + indice: 0.41MB + motore InnoDB
vmktf_newsletter_user_logs: Dati: 0.08MB + indice: 0.00MB + motore InnoDB
vmktf_nf_objectmeta: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_nf_objects: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_nf_relationships: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_ninja_forms_fav_fields: Dati: 0.05MB + indice: 0.00MB + motore InnoDB
vmktf_ninja_forms_fields: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_optins: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
vmktf_optin_meta: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
vmktf_options: Dati: 5.52MB + indice: 0.20MB + motore InnoDB
vmktf_pmxe_exports: Dati: 0.23MB + indice: 0.00MB + motore InnoDB
vmktf_pmxe_google_cats: Dati: 0.39MB + indice: 0.00MB + motore InnoDB
vmktf_pmxe_posts: Dati: 1.52MB + indice: 0.00MB + motore InnoDB
vmktf_pmxe_templates: Dati: 0.03MB + indice: 0.00MB + motore InnoDB
vmktf_pmxi_files: Dati: 0.01MB + indice: 0.00MB + motore MyISAM
vmktf_pmxi_history: Dati: 0.01MB + indice: 0.00MB + motore MyISAM
vmktf_pmxi_images: Dati: 0.06MB + indice: 0.00MB + motore InnoDB
vmktf_pmxi_imports: Dati: 3.20MB + indice: 0.00MB + motore MyISAM
vmktf_pmxi_posts: Dati: 0.07MB + indice: 0.03MB + motore MyISAM
vmktf_pmxi_templates: Dati: 0.02MB + indice: 0.00MB + motore MyISAM
vmktf_postmeta: Dati: 18.55MB + indice: 6.03MB + motore InnoDB
vmktf_posts: Dati: 3.52MB + indice: 0.86MB + motore InnoDB
vmktf_pp_login_builder: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_pp_password_reset_builder: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_pp_registration_builder: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_registration_log: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_revslider_css: Dati: 0.14MB + indice: 0.02MB + motore InnoDB
vmktf_revslider_layer_animations: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_revslider_navigations: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_revslider_settings: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_revslider_sliders: Dati: 0.08MB + indice: 0.02MB + motore InnoDB
vmktf_revslider_slides: Dati: 0.17MB + indice: 0.02MB + motore InnoDB
vmktf_revslider_static_slides: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_signups: Dati: 0.02MB + indice: 0.06MB + motore InnoDB
vmktf_site: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_sitemeta: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
vmktf_smush_dir_images: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
vmktf_taxonomymeta: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
vmktf_termmeta: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
vmktf_terms: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
vmktf_term_relationships: Dati: 0.09MB + indice: 0.06MB + motore InnoDB
vmktf_term_taxonomy: Dati: 0.06MB + indice: 0.03MB + motore InnoDB
vmktf_uji_counter: Dati: 0.00MB + indice: 0.00MB + motore MyISAM
vmktf_uji_subscriptions: Dati: 0.00MB + indice: 0.00MB + motore MyISAM
vmktf_usermeta: Dati: 0.48MB + indice: 0.50MB + motore InnoDB
vmktf_users: Dati: 0.06MB + indice: 0.05MB + motore InnoDB
vmktf_vtprd_purchase_log: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_vtprd_purchase_log_product: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_vtprd_purchase_log_product_rule: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_waiting: Dati: 0.00MB + indice: 0.00MB + motore MyISAM
vmktf_wc_admin_notes: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_wc_admin_note_actions: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_wc_category_lookup: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_wc_customer_lookup: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
vmktf_wc_download_log: Dati: 0.00MB + indice: 0.00MB + motore MyISAM
vmktf_wc_order_coupon_lookup: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
vmktf_wc_order_product_lookup: Dati: 0.02MB + indice: 0.06MB + motore InnoDB
vmktf_wc_order_stats: Dati: 0.02MB + indice: 0.05MB + motore InnoDB
vmktf_wc_order_tax_lookup: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
vmktf_wc_product_meta_lookup: Dati: 0.27MB + indice: 0.64MB + motore InnoDB
vmktf_wc_reserved_stock: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_wc_tax_rate_classes: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_wc_webhooks: Dati: 0.00MB + indice: 0.00MB + motore MyISAM
vmktf_wfblockediplog: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_wfblocks7: Dati: 0.00MB + indice: 0.00MB + motore MyISAM
vmktf_wfconfig: Dati: 1.52MB + indice: 0.00MB + motore InnoDB
vmktf_wfcrawlers: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_wffilechanges: Dati: 0.00MB + indice: 0.00MB + motore MyISAM
vmktf_wffilemods: Dati: 4.52MB + indice: 0.00MB + motore InnoDB
vmktf_wfhits: Dati: 0.02MB + indice: 0.05MB + motore InnoDB
vmktf_wfhoover: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_wfissues: Dati: 0.02MB + indice: 0.06MB + motore InnoDB
vmktf_wfknownfilelist: Dati: 1.52MB + indice: 0.00MB + motore InnoDB
vmktf_wflivetraffichuman: Dati: 0.00MB + indice: 0.00MB + motore MyISAM
vmktf_wflocs: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_wflogins: Dati: 0.30MB + indice: 0.14MB + motore InnoDB
vmktf_wfls_2fa_secrets: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_wfls_settings: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_wfnotifications: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_wfpendingissues: Dati: 0.02MB + indice: 0.06MB + motore InnoDB
vmktf_wfreversecache: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_wfsnipcache: Dati: 0.02MB + indice: 0.05MB + motore InnoDB
vmktf_wfstatus: Dati: 0.16MB + indice: 0.11MB + motore InnoDB
vmktf_wftrafficrates: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_wow_countdowns_free: Dati: 0.00MB + indice: 0.00MB + motore MyISAM
vmktf_wpie_template: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
vmktf_wsluserscontacts: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_wslusersprofiles: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
vmktf_yoast_indexable: Dati: 2.52MB + indice: 0.72MB + motore InnoDB
vmktf_yoast_indexable_hierarchy: Dati: 0.06MB + indice: 0.05MB + motore InnoDB
vmktf_yoast_migrations: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
vmktf_yoast_primary_term: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
vmktf_yoast_seo_links: Dati: 0.06MB + indice: 0.02MB + motore InnoDB
vmktf_yoast_seo_meta: Dati: 1.52MB + indice: 0.00MB + motore InnoDB### Post Type Counts ###
attachment: 2526
avia_framework_post: 33
boxzilla-box: 12
custom_css: 3
customize_changeset: 25
flamingo_contact: 24
flamingo_inbound: 61
footer: 2
mc4wp-form: 2
nav_menu_item: 142
nf_sub: 14
oembed_cache: 7
page: 42
popup: 1
popup_theme: 6
post: 15
product: 41
product_variation: 453
product-feed: 1
revision: 275
shop_coupon: 67
shop_order: 265
shop_order_refund: 9
sidebar: 2
vc_settings_preset: 2
wcct_countdown: 1
wpcdt_countdown: 1
wpcf7_contact_form: 7
xlwcty_thankyou: 1### Security ###
Secure connection (HTTPS): ✔
Hide errors from visitors: ✔### Active Plugins (16) ###
Boxzilla: by ibericode – 3.2.23
Classic Editor: by Contributori WordPress – 1.6
Coming Soon Page, Under Construction & Maintenance Mode by SeedProd: by SeedProd – 5.1.3
Duplica pagina: by mndpsingh287 – 4.2
Google Tag Manager for WordPress: by Thomas Geiger – 1.11.4 – Versione installata non testata con versione attiva di WooCommerce 4.4.1
Google Customer Reviews for WooCommerce: by eCreations – 2.6.12 – Versione installata non testata con versione attiva di WooCommerce 4.4.1
Private Store For WooCommerce: by CodeIncept – 1.0.3 – Versione installata non testata con versione attiva di WooCommerce 4.4.1
SG Optimizer: by SiteGround – 5.6.5
WebP Converter for Media: by Mateusz Gbiorczyk – 1.4.2
Variation Swatches for WooCommerce: by Emran Ahmed – 1.0.85 – Versione installata non testata con versione attiva di WooCommerce 4.4.1
WooCommerce Extra Charges To Payment Gateway (Standard): by hemsingh1 – 1.0.12.9 – Versione installata non testata con versione attiva di WooCommerce 4.4.1
WooCommerce Stripe Gateway: by WooCommerce – 4.5.2 – Versione installata non testata con versione attiva di WooCommerce 4.4.1
WooCommerce: by Automattic – 4.4.1
Wordfence Security: by Wordfence – 7.4.10
Yoast SEO: by Team Yoast – 14.8.1
Smush: by WPMU DEV – 3.6.3### Inactive Plugins (14) ###
Advanced Order Export For WooCommerce: by AlgolPlus – 3.1.5
Contact Form 7: by Takayuki Miyoshi – 5.2.1
Disable Gutenberg: by Jeff Starr – 2.2
Envato Market: by Envato – 2.0.3
HookMeUp – Additional Content for WooCommerce: by GetBowtied – 1.3.1
Magic Embeds: by Miguel Sirvent – 3.0.8
Mr. Tailor Extender: by GetBowtied – 1.3.7
Newsletter: by Stefano Lissa & The Newsletter Team – 6.8.5
NextMove Lite – Thank You Page for WooCommerce: by XLPlugins – 2.12.0 – Versione installata non testata con versione attiva di WooCommerce 4.4.1
WooCommerce Product Feed Manager: by RexTheme – 5.38 – Versione installata non testata con versione attiva di WooCommerce 4.4.1
WP All Export: by Soflyy – 1.2.7
WP All Import – WooCommerce Add-On Pro: by Soflyy – 3.2.2 – Versione installata non testata con versione attiva di WooCommerce 4.4.1
WP All Import Pro: by Soflyy – 4.6.1
WPBakery Page Builder: by Michael M – WPBakery.com – 6.1### Settings ###
API Enabled: ✔
Force SSL: –
Currency: EUR (€)
Currency Position: left_space
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: #7458 – /collezione/
Carrello: #42865 – /carrello/
Pagamento: #7452 – /completa-transazione/
Il mio account: #7442 – /my-account/
Termini e condizioni: #44134 – /condizioni-generali-di-vendita/### Theme ###
Name: Enfold Child
Version: 1.0
Author URL: http://kriesi.at
Child Theme: ✔
Parent Theme Name: Enfold
Parent Theme Version: 4.7.4
Parent Theme Author URL: https://kriesi.at
WooCommerce Support: ✔### Templates ###
Overrides: –
### Action Scheduler ###
Completato: 46
Oldest: 2020-07-30 10:39:24 +0200
Newest: 2020-08-26 17:36:36 +0200In attesa: 1
Oldest: 2020-08-29 05:13:58 +0200
Newest: 2020-08-29 05:13:58 +0200`
WordPress 5.5–de_DE_formal with enabled jquery migrate helper, Enfold 4.7.6.3
Hi Guys,
unfortunately the pagination of the masonry gallery does not work anymore at a customers site. I’ve put all relevant details in the private fields. When clicking on a page number it just reloads the first page. No caching plugin is used (deleted to check if it is causing the problem, was comet cache, cache folder deleted) even lazy loading on the masonry is disabled.
Any help would be highly appreciated!
Thanks in advance & Cheers,
– onlylettersandnumbers
There is a bug in Advanced Layout Builder when Slider Revolution is active.
When editing / adding text to any ALB form field – e.g. Special Headng / Image Alt / Custom CSS Class etc – the space character does not work.
For example – Add a text block and clicking the space bar adds a space character in the Visual Editor but switch to the plain text editor and it does not. Similarly try to add a space to any text in a field under Image Attachment Details and the space bar does not work. Basically the space bar does not work on any ALB field except the visual editor with revslider activated.
Disable Slider Revolution and the bug is gone.
Tested Firefox & Chrome.Vanilla install test site details below for you to confirm – WordPress 5.5 (latest) | Enfold Version 4.7.6.3 (latest) | Slider Revolution Version 6.2.21 (latest) only. Confirm bug exists on localhost and all web hosts tested.
I can confirm that this issue appeared as a result of upgrading WordPress to 5.5.
Please try and confirm.
Thanks.
In reply to: Avia Layout
Hey zibbaldone,
Those settings are only if you want to override the settings which has been set for the image in the WordPress gallery. If you don’t want to override the default settings, then don’t put anything in those fields.
Custom Alt Attribute
Add a custom alt attribute limited to this instance, replaces media gallery settings.I’m not sure what you mean by this:
Avia Layout guide
Could you try to explain a bit further please?
Best regards,
RikardHi guys,
I have removed some unnecessary fields in woocommerce with php.
When you go to the checkout form, the Product information box now overlaps the “Your order” heading. The payment box is cutoff on the bottom.
The checkout form on mobile is a mess too. The two columns display next to each other (1) in portrait mode, but there is not enough room for that on mobile. The landscape mode looks great, but with both modes the payment information is even more cutoff. (2 & 3)
This is the code you guys helped me with a while ago to style the checkout page:
/* Styling woocommerce checkout */ .col2-set .col-2 { float: none !important; } #order_review, #order_review_heading { clear: both !important; width: 40% !important; float: right !important; } #order_review { position: absolute; top: 11.5%; right: 0; } #order_review_heading { position: absolute; top: 6.8 %; right: 0; } #top .checkout .col-1, #top .checkout .col-2 { clear: both !important; width: 100% !important; } #customer_details { width: 40% !important; float: left !important; clear: both !important; }I’ve tried multiple CSS fixes until my head exploded. I’m missing something, but I can’t figure out what.
My question: How do I create more room for the checkout page on desktop and make it responsive on mobile without anything being cutoff? :)
Sincerely,
MortickaIn reply to: use CPT instead of page for "Page Content" element
here’s a workaround in the meantime…
(it’s basically a shortcode that runs a shortcode that pulls in content from another CPT post with Builder content)1) add a CPT eg “component”
2) install the plugin Custom Content Shortcodes (CCS) https://en-gb.wordpress.org/plugins/custom-content-shortcode/
3) enable the Meta Shortcodes option in CCS settings
4) create a CCS Shortcode called “component” and add this code into the editor
[content type=component name={NAME}]
(this uses CCScontentfunction to pull content/fields from another post)5) add this code to your
functions.phpto enable the Avia Builder in your CPT’s content editor// add Avia Builder to CPTs function avf_alb_supported_post_types_mod( array $supported_post_types ) { $supported_post_types[] = 'component'; return $supported_post_types; } add_filter('avf_alb_supported_post_types', 'avf_alb_supported_post_types_mod', 10, 1);you can now add this to HTML/text blocks etc in your pages, to pull in the
contentfield from your CPT (ie our builder content)
[component name="my-component"](You could of course just use
[content type=component name="my-component"]but I’ve added the proxy shortcode to keep it a little bit more readable)In reply to: enfold update
Hi
The right-left is the only plus we flound untill now with the upgrade – as it is RTL Support with is very important for hebrew and the old enfold did not have the support.Part from that if you look at the homepage you can see a HUGE diffrance with styles – and the innerpages are also stripped from their border and the custom fields also vanished. See the attached screen capture of both site side by side.
Please help us to restor the designs on the new enfold so we can continue – this is a major setback for site updates and marketing.
You kind help is needed ASAP.
Thanks in advanced,
AviHey fruntkeMarcel,
Thank you for the inquiry.
You can use the “avf_google_recaptcha_badge_content” filter to adjust the recaptcha badge content or insert additional info to it.
Example:
add_filter('avf_google_recaptcha_badge_content', function($badge) { // $badge = '<div class="av-google-badge-message hidden">'; // $badge .= __( 'This site is protected by reCAPTCHA and the Google <a href="https://policies.google.com/privacy">Privacy Policy</a> and <a href="https://policies.google.com/terms">Terms of Service</a> apply.', 'avia_framework' ); // $badge .= '</div>'; // $badge .= "<div class='custom-badge-content'>Additional Badge Content</div>"; return $badge; }, 10, 1);You can also use the “avf_sc_contact_form_elements” filter to insert custom form fields.
Best regards,
IsmaelIf you click ” see all results” after a search in the search bar – the result page shows following PHP errors:
Warning: strtolower() expects parameter 1 to be string, array given in /customers/7/7/3/goedkoopdrank.be/httpd.www/wp-includes/formatting.php on line 2151 Warning: strtolower() expects parameter 1 to be string, array given in /customers/7/7/3/goedkoopdrank.be/httpd.www/wp-includes/formatting.php on line 2151 Warning: strtolower() expects parameter 1 to be string, array given in /customers/7/7/3/goedkoopdrank.be/httpd.www/wp-includes/formatting.php on line 2151 Warning: strtolower() expects parameter 1 to be string, array given in /customers/7/7/3/goedkoopdrank.be/httpd.www/wp-includes/formatting.php on line 2151 Warning: strtolower() expects parameter 1 to be string, array given in /customers/7/7/3/goedkoopdrank.be/httpd.www/wp-includes/formatting.php on line 2151 Warning: strtolower() expects parameter 1 to be string, array given in /customers/7/7/3/goedkoopdrank.be/httpd.www/wp-includes/formatting.php on line 2151You can see it here LIVE
https://www.goedkoopdrank.be/?s=coca&numberposts=5&post_type%5B0%5D=product&results_hide_fields=In reply to: Blog Post preview does not show titel
Hi Andre,
1- You had following code in Enfold theme options > General Styling > Quick CSS field and in Appearance > Customize > Additional CSS fields
.entry-title { display:none; }I deleted them.
2- I added following code to Quick CSS to increase the width on single blog
/* Increase single blog layout */ #top .fullsize .template-blog .post .entry-content-wrapper, #top .fullsize .template-blog .post .entry-content-wrapper > * { max-width: 100%; }3- That pencil icon is a placeholder that shows when you do not upload a featured image. I added following code to Quick CSS to remove it
/* Remove featured image placeholder */ #top .fullsize .template-blog .blog-meta, .avia-content-slider .fake-thumbnail .slide-image { display: none; }If you are going to upload featured images to your posts in future, please do not forget to remove this code.
Please review your website :)
Regards,
Yigit
