Your site is protected so none can see the issue. Opacity applies to the element and it’s childs. If you want to have background opacity you need to use the CSS property background-color: rgba(255,255,255,0.7). The decimal on the fourth place is the alpha channel and defines the opacity.

@zaccc I totally understand what you are saying. But I am a developer and I know software has no warranties. It is the nature of open source development. You expect something that simply is not possible. Even in closed source development you wont get a guaranty for the software doing what you want. And this is where the advantages of open source development and the spirit of wordpress come in. If there is a bug anyone able and willing to help can fix it.

You simply can’t say Kriesi missed it. Look at other themes they even are not willing to support the new gallery from WooCommerce 3. They remove it and continue with their own solution. And even WooCommerce 3 was not perfect on day one. We are close to version 3.0.5 and still daily new issues are revealed. Many of them so rare that you even could not think of before. I know it is difficult for end users and for non-developers to understand whats happening behind the scenes.

If eCommerce is your business than you have to test yourself every aspect before updating. I can post a list of more then 40 well known WooCommerce plugins and themes that stopped working after updating to woocommerce 3. You can’t expect them all to work within a few days after a major WooCommerce release hits the market.

So don’t push your self. Simply wait. And if Enfold gets a new version wait again. Visit the forum. Use the search and read what others say. If there are no complaints for a week install it on development server and test it with your plugins. If all works role out the update to your production environment.

@katestuartdesign to make the child theme break the permalinks there would have to be a function call within the child themes functions.php that could cause it. Thus enabling the parent theme again would fix the issue? Does it? Have you disabled any other plugin for testing? The amount of root causes for this issue is very limited and turns down to the .htaccess file and the rewrite rules array in wordpress. If it worked before in the same installation without any changes except the child theme, than definitely something must habe been added to the child theme causing the rewrite array to get corrupted (like adding custom post types the wrong way). One possible issue coud be the provided switched of the apache mod_rewrite mdule but that is unlikely to happen.

Would you mind trying to change the permission of .htaccess to rw-rw-r– (chmod 664) and save the permalinks again? The permission it has now is totally perfect IF php is running as fast-cgi or php-fpm. However it won’t work if php is running as mod-php within the apache webserver.

@zaccc, @georg, @adriansmithuk I just tried to help. A few hundred people are happy to using my solution. You don’t need to use it.

@KateStuartDesign make sure your .htaccess file is writeable by the webserver. The issue you describe happens if wordpress cant modify the .htaccess file for pretty permalinks

@Zacc the solution has been posted a hundred times. Even in this thread here.

You may have tried it while your site was protected. Facebook is caching the scrap so you will see this error for some time. In such case use the developer interface of facebook an scrap the site again. I just did that with your page and it is working now.

@kbarranco this would need some custom development.

1. Create a child theme if not already using one
2. Create a monkey patch to overload Enfolds lightbox defaults

(function($){
	var _old_avia_lightbox = $.fn.avia_activate_lightbox;
	$.fn.avia_activate_lightbox = function( variables ){
		if ( ! variables ) {
			var variables = {};
		}
		variables.groups = [];
		variables.autolinkElements = '';
		variables.videoElements = '';
		return _old_avia_lightbox.call( this, variables );
	};
})(jQuery);

3. Store the patch in a custom jquery file like my_scripts.js and copy it to your child themes directory
4. Enqueue the file conditionally from you child theme functions.php

add_action( 'wp_enqueue_scripts', 'load_my_scripts', '99' );
function load_my_scripts() {
    global $post;
    $keep_lightbox = array('slug-of-page-to-keep-lightbox', 'slug-of-an-other-page-to-keep-lightbox', 'slug-of-even-an-other-page-to-keep-lightbox');
    if( ! in_array( $post->post_name, $keep_lightbox ) ){
      wp_enqueue_script( 'my-scripts', get_stylesheet_directory_uri() . '/my_scripts.js', array( 'jquery', 'avia-default' ) );
    }
}

The lighbox will only be active on those pages defined in $keep_lightbox. However this will not remove the link from the images and clicking on them will you open the attachment in the browser.

@waveshaper although you can throw CSS on many issues to ‘solve’ them (it’s hiding not solving) the way to remove the category count in WooCommerce is to add the following function to the functions.php of your child theme:

add_filter( 'woocommerce_subcategory_count_html', '__return_empty_string' );

@micoenfold

p.demo_store {
    position: fixed;
    top: inherit;
    left: 0;
    bottom: 69px;
    right: 0;
    margin: 0;
    padding: 1em 1.41575em;
    background: -webkit-linear-gradient(#3D9CD2, #3D9fff);
    z-index: 999;
}

@alexbanga

CAUTION! Do not downgrade to 2.4.16 if you got new orders since you upgraded to 3.0.4.
This said you can follow the official guide to downgrade
AGAIN! Do not downgrade to 2.4.16 if you got new orders since you upgraded to 3.0.4.

If you need to stay with 3.0.4 just make sure you have Enfold 4.0.5 running any apply my solution. It is save to use and works on hundreds of Enfold installations.

@alsterb take a look here

@gertbach take a look at https://booster.io. They have some nice currency modules

Hallo Frau Fütterer, haben Sie meinen Beitrag gelesen?