justinbitter

I agree they should atleast do more robust testing so that it doesn’t break on simple things. That being said somewhere i do get they probably use us as beta testers for features/updates. I would probably also do that if i was unsure of my code and want to quickely see where the problems arise and keeping in mind of very tight deadlines. Not something fun to do since you want to make a great product but that is how it goes.

That’s why in these cases i always recommend people/devs to test new versions on a stage site locally or a test server. You could also try using wp staging plugin.

I think it somehow also relates to browser data i don’t know if that is correct but i had the same issue where i could not edit the footer. I just logged into firefox (mostly i use chrome) where there is no user data no history nothing and just logged into the website and it worked. Ofcourse to note i also updated to the most recent versions of elementor free and UAE.

Thanks i really appreciate it. I think i’ll go with the third option since i have too many users to change the roles now. Again thanks!

That is why i choose to use a actual form builder. And elementor to just build the website.

If your term description is much longer than better to use this. It worked for my site very well. This was generated using claude ai ??

.term-description {
    /* Set initial fixed height */
    max-height: 200px; /* Adjust this value as needed */
    
    /* Hide overflowing content */
    overflow: hidden;
    
    /* Add a smooth transition effect */
    transition: max-height 0.5s ease;
    
    /* Optional: Add a subtle shadow to indicate more content */
    position: relative;
    margin-bottom: 2em;
}

.term-description::after {
    /* Create a gradient overlay at the bottom to indicate more content */
    content: "";
    position: absolute;
    bottom: 0;
    left: 0;
    width: 100%;
    height: 50px; /* Height of the gradient */
    background: linear-gradient(to top, white, rgba(255, 255, 255, 0));
    pointer-events: none; /* Allow clicks to pass through */
    transition: opacity 0.5s ease;
}

.term-description:hover {
    /* Expand to show full content */
    max-height: none; /* Set to none to show full content */
}

.term-description:hover::after {
    /* Hide the gradient overlay when expanded */
    opacity: 0;
}

I have found the problem. It seems the labels for the italian and spanish version were not set to active. That fixed the problem. Thanks for the help btw!

Hi, the site uses wpml for translation. As you can see they have been translated execept for the the first one that is not important.

• This reply was modified 5 months, 1 week ago by justinbitter.

For example, when I try to add an attribute to a product using the bulk editor, it shows as saved, but after refreshing the page, the change disappears. The attribute only saves correctly when added through the standard WooCommerce editor.

@giuliopanda yes i get the same type of error when trying to bulkresize the images

if there are other things i need to do before that please let me know @power2009

Hi @power2009 i tried your code that you provided and well i’m stuck with this error

// Load the image and convert it to true color if necessary

            $image = wp_get_image_editor($file_path);

            if (!is_wp_error($image)) {

? ? ? ? ? ? ? ? $image_resource = $image->get_image(); —-> this is giving me error

                $image_resource = $this->convert_to_truecolor($image_resource);

                $image->save($file_path, null, $quality);

? ? ? ? ? ? }

probably because it doesn’t exist. can you help me get this right since i don’t know code that well.