Forum Replies Created

Viewing 15 posts - 1 through 15 (of 527 total)
  • Author
    Posts
  • Michael C
    Keymaster
    Post count: 527

    It might be that you need to refresh the studio data. You can do that from the studio page on the back-end:

    Michael C
    Keymaster
    Post count: 527

    The emails are now handled on a separate tab called notifications. If you switch to that tab you can set the email(s) which you want to be sent.

    Note: documentation and videos are in progress for that.

    • This reply was modified 1 month, 1 week ago by Michael C.
    Michael C
    Keymaster
    Post count: 527

    Its not 100% clear, but if you mean you updated the theme from 7.2 > 7.7, then the plugins will also need to be updated. The error is due to the fact that they aren’t. You may get around that particular error by editing the code, but you will definitely have many many more issues beyond that with mismatched versions that differ that much.

    Just looking through the file history, we actually removed that function call from fusion-blog in version 6 of Avada (2.0 Builder). So at least 2.5 years ago. That plugin will definitely not be compatible with the theme at 7.7.

    Michael C
    Keymaster
    Post count: 527

    Which versions of Avada and Avada Builder do you have? The function in your error log no longer exists in 7.7. Which makes me think either the versions are mismatched and something needs to be updated or that the file has been edited.

    Michael C
    Keymaster
    Post count: 527

    We have released a patch for this issue:

    #420508 – Apr. 13, 2022
    Prevent incorrect child element encoding after back-end builder edit.

    The problem occurs when a child element is edited using the back-end builder. Other child elements within the same parent element become escaped. Note, the patch only prevents this from happening again. For content which has already been escaped the content will need to be edited and re-saved.

    Michael C
    Keymaster
    Post count: 527
    in reply to: Configurator #876901

    Hi,

    What exactly do you mean by a configurator? Some more information would help here.

    Thanks

    Michael C
    Keymaster
    Post count: 527

    If you have lazy loading on then only the visible image will be loaded in both cases. But the markup will be doubled so the page length will be longer. If you just have a background image and some text, then in the end it shouldn’t have much of an impact.

    Michael C
    Keymaster
    Post count: 527

    Hi,

    The logic there is based on the device rather than the width. If you want it based on width you can use the visibility options (small, medium, large) rather than the display logic. However, for performance, you are better off using the device logic instead. Real users are not going to load the site and manually resize their browser.

    Thanks

    Michael C
    Keymaster
    Post count: 527

    It looks like the add-on needs to update its function call. I suggest contacting the plugin author, the new method is Fusion_Color::new_color( $value )->is_color_transparent()

    Michael C
    Keymaster
    Post count: 527

    Did you disable the element again? If so, please leave it enabled and check if the warning still shows (it shouldn’t).

    Michael C
    Keymaster
    Post count: 527

    Hi,

    Go to Global Options > Avada Builder Elements – Icon Element and check what is set for Border Radius. It sounds like an invalid value is set there. If you fill in the 4 border radius inputs it should stop the warning.

    Thanks

    Michael C
    Keymaster
    Post count: 527

    Hi,

    Sorry about that, the filter will be available in 7.5, which hasn’t been released yet. It should be out soon though and then the code will work.

    Thanks

    Michael C
    Keymaster
    Post count: 527

    Hi,

    We do have a filter for this mechanism. The first parameter is the unique filename, the second is the original filename. Adding something like the following to a child theme should return the original instead:

    add_filter( 'awb_forms_upload_file_name', 'original_file_name', 10, 2 );
    function original_file_name( $unique, $filename ) {
    	return $filename;
    }

    Please note though. Depending on what you are allowing to be uploaded this could prevent a security issue. Since the person uploading will know the filename as stored on the server.

    Michael C
    Keymaster
    Post count: 527

    Hi,

    The name there should be written GET variable with capitals. Since it is referring to https://www.php.net/manual/en/reserved.variables.get.php. It terms of usage that means checking for a variable in the current address and hiding or showing.

    Eg you could have a URL such as https://avada.theme-fusion.com/?reference=facebook. But you link people from different sources with different values. Based on that you then show different content. You would check for GET variable reference.

    Note though, ACF and custom fields will be added to the list for 7.5.

    Thanks

    Michael C
    Keymaster
    Post count: 527

    If the UI toolbar is blinking, it sounds like it might be the browser and CSS filters. Alternatively, it could be position absolute content overlaying. If it is either of those, you can click the preferences icon in the top toolbar of the live editor and find options. In there you can then turn off Enable Transparent Header & Absolute Containers and Enable Preview for Filter Options to see if either of those are the problem.

Viewing 15 posts - 1 through 15 (of 527 total)