Forum Replies Created
-
AuthorPosts
-
Hi,
Thank you for reporting this. Something we have completly missed.
For next release I will add a fix for this in av_video_assets_required.
I will let you know here when the fix is ready so you can update the file.Meanwhile you can use filter avf_enqueue_wp_mediaelement to avoid loading (in functions.php line 679).
Return false when not needed.Best regards,
GünterSeptember 15, 2023 at 11:22 am in reply to: Unexpected : DOMException: Failed to load because no supported source was found #1419266September 14, 2023 at 3:35 pm in reply to: Unexpected : DOMException: Failed to load because no supported source was found #1419172Hi,
Also die einzige vernünftige Erklärung die ich habe ist, dass pagespeed da es nichts von der Seite anzeigt, das Laden des videos blockiert, der HTML DOM aber da ist und dann natürlich unser js darauf zugreift und ausgeführt wird.
Wenn ich mit einem video element auf ein nicht vorhandenes Video zugreife (localhost) dann bekomme ich in lighthouse:
Failed to load resource: the server responded with a status of 404 (Not Found)
Best regards,
GünterHi Jeannette,
Thank you for the feedback.
I will leave this topic open.
Enjoy the theme and have a great day.
Best regards,
GünterSeptember 13, 2023 at 3:51 pm in reply to: Unexpected : DOMException: Failed to load because no supported source was found #1419054Hi,
Thanks for the login credentials.
As you said: the staging site works as expected.
When saving theme options the post css files get invalidated (this happens in database) and are regenerated when a page is loaded in front.
You can check this on your staging site with ftp in folder /wp-content/uploads/dynamic_avia/avia_posts_css/.
You need to reload theme options page after save to start a cron job to delete the post css files and also reload (“aktualisieren”) the directory in your ftp client.Checking the source text of your productive system page there are the correct links to the post css file (see private content).
It seems, that the files could not be created on your production site.
Can you recheck if there are limitations in the filesystem ?
Are cron jobs enabled?
There is folder /wp-content/uploads/avia_posts_css – this is an outdated folder that you can delete (was moved inside /dynamic_avia.
Can you scan your filesystem, if you find post-37241.css somewhere.Best regards,
GünterSeptember 13, 2023 at 12:38 pm in reply to: Unexpected : DOMException: Failed to load because no supported source was found #1419030Hey Guenter,
Having a quick look into it:
WP Media Element (html tag mediaelementwrapper) used in ALB Video element has a structure as described in your link
in Danger Zone:<video ....> <source scr="...." ...>
where the play() promise never rejects. So the solution probably cannot be used.
Maybe the HTML structure is different depending where you encounter the problem.
There does not seem to be an easy and quick solution.
Best regards,
GünterSeptember 12, 2023 at 11:26 am in reply to: Long page loading ends with 50x due to false SVG logo url #1418873Hey aixhibitag,
Thank you for using Enfold and reporting this.
For next release I added a timeout to the curl options when reading the svg file.
This fixed it on my dev site. I tested it with attachment ID -> missing file and adding wrong url.If you want to check it replace enfold\framework\php\class-svg-images.php with the content of
Best regards,
GünterHi Jason,
Thank you for using Enfold and for your patience.
I want to give you a quick overview on what will be coming:
We are currently working on the integration of custom fields content in ALB elements and to get most out of this feature on “Custom Page Layouts”.
This means based on ALB you can design editable page layouts and use these to display your pages, posts and custom post type posts.
But we cannot give a release date yet.
Best regards,
GünterHey Guenter,
Actually $shrink_factor is intended to be integer.
In enfold\js\avia-snippet-sticky-header.js around line 146 you find:
const value = parseInt( shrink_factor );
This results to 0 with 0.1 so it should acutally work (header remains unshrinked)
Best regards,
GünterHi,
Problem caused by double enqueue of scripts avia_sidebar.js (and avia_sidebar.css).
In case of min files both files were enqueued (class avia_sidebar always used unminified version).
To fix the problem please replace enfold\framework\php\class-sidebar-generator.php
with the content of
Best regards,
GünterHi,
The HPOS is “only” affecting the way orders are saved in own tables. This means, that the “normal” WP way to access post metadata does no longer work. You need to use the WC Order API to get access to order data.
As Enfold does not do anything with orders there should be no conflict.
WC has a development beta https://github.com/woocommerce/woocommerce/releases/tag/feature-custom-order-table to test it. I did not see any problems testing it a few months ago.
Best regards,
GünterHi,
I tagged Yigit for this topic. He will come back to you in case he needs more info for the docu.
We appreciate your help.
Best regards,
GünterHi,
Thanks for providing insight into relevanssi and that it helps on large sites and works well with Enfold.
Have a great day.
Best regards,
GünterAugust 2, 2023 at 4:33 pm in reply to: (get_page_by_title() function has been deprecated scince 6.2.0) #1415264Hi,
Thank you for your feedback and that it is solved.
Enjoy the theme and have a great day.
Best regards,
GünterHey Guenter,
Strange – no, I cannot reproduce on my dev install.
Anything special on these installs ?
Best regards,
GünterHi,
Filter will be in 5.6.6:
searchform.php
This is the default that a form collects all input on submit.
Try this (adding the disabled attribute):
Best regards,
GünterHi,
If this is a solution I can add a filter for next release.
Just let me know.Best regards,
GünterHi,
Have a look into enfold\config-relevanssi\class-avia-relevanssi.php
Around line 170 you find:
$tempquery->query_vars = $search_parameters; relevanssi_do_query( $tempquery );
Try the following:
$tempquery->query_vars = $search_parameters; $tempquery->set( 'posts_per_page', 5 ); relevanssi_do_query( $tempquery );
Best regards,
GünterHey Thomas,
I did not dig deeper in it, but when the full search result page does not use ajax you could try:
if( wp_doing_ajax() ) { add_filter( 'pre_option_relevanssi_throttle_limit', function( $limit ) { return 5; } ); }
Best regards,
GünterHey HenkN,
To functions.php of your child theme add:
add_theme_support( "avia_template_builder_custom_post_type_grid" );
This will add an additional selectbox “Which Entries Should Be Used” to ALB Portfolio Grid where you can select “Post Tags”
The portfolio grid filter (line 1589):
$query = apply_filters( 'avia_post_grid_query', $query, $params );
$query is the WP array rendered to WP_Query with:
$this->entries = new WP_Query( $query );
So you are able to modify this and use all the capabilites WP_Query (https://developer.wordpress.org/reference/classes/wp_query/) offers
Best regards,
GünterHi,
Glad we could help you.
Enjoy the theme and have a great day.
Best regards,
GünterHey emilconsor,
Falls Ihr mit einem child theme arbeitet, dann fügt in functions.php des child themes am Ende den folgenden Code ein:
add_theme_support( 'show_advanced_custom_element_options' );
Dann gibt es unter “Custom Elements” — “Show Advanced Options” die Selectbox “Custom Elements For Subitems” (Theme options page neu laden !!).
Dort dann “Individually select subitem custom element templates” auswählen.
Siehe auch https://kriesi.at/documentation/enfold/custom-element-templates/#custom-elements-advanced-options
Best regards,
GünterHey Brugmedia,
Sorry for the problem.
Please see this answer: https://kriesi.at/support/topic/problem-with-update-version-5-6-4/#post-1414377
If you need help, let us know.
Best regards,
GünterHey kreativeseite,
Thank you for using Enfold.
This is “only” a warning and does not have a negative effect.
We have fixed it in 5.6.5
To get rid of it please replace enfold\config-templatebuilder\avia-shortcodes\blog\blog.php
with the content of
Do not forget to make a backup of the original file for a fallback and clear server and browser cache.
If you need help let us know.
Best regards,
GünterHi @boehmmedia,
As already mentioned before: our loop-search.php uses the default WP loop.
You must hook in the default WP search query and alter this to return the results in the order you need. Maybe these articles helps you:
https://stackoverflow.com/questions/52317953/change-search-query-wordpress
https://stackoverflow.com/questions/9468804/make-wordpress-search-only-in-post-titleBut maybe it is a better idea to use a standard WooCommerce extension like
Best regards,
GünterHey Tim,
Sorry for the late reply.
Please check enfold\css\layout.css
Around line 2076 you find:
.ajax_load_inner{ background: url("../images/layout/loading.gif") no-repeat scroll center center #fff; opacity: 0.5; position: absolute; top:0; left:0; right:0; bottom:0; }
I think this is what you need.
To override it you can use selector:
#searchform .ajax_load .ajax_load_inner{ }
Hope this helps you.
Best regards,
GünterHey Thomas,
Thanks for reporting this – and sorry for the problem.
I think I found the problem.
Can you please replace
enfold\config-woocommerce\config.php
with the content of
https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_5_6_4/woocommerce/config.php
Do not forget to clear server and browser cache and make a backup of the original file for a fallback.
Best regards,
Günter -
AuthorPosts