Forum Replies Created

Viewing 15 replies - 1 through 15 (of 41 total)
  • Plugin Support Diana Burduja

    (@dianaburduja)

    Added the option in version 3.52.

    Plugin Support Diana Burduja

    (@dianaburduja)

    Fixed in version 3.52.

    Plugin Support Diana Burduja

    (@dianaburduja)

    Hello Klaus,

    on my side, after backing up and restoring the backup with the WPvivid plugin, everything works alright, but only if the backup includes the database and the files.

    If you don’t want to open each custom code and click the “Save” button, then you could generate a “WordPress Files (Exclude Database)” backup for the development website and then restore it on the production website.

    Plugin Support Diana Burduja

    (@dianaburduja)

    Hello @audads,

    thank you for the suggestion.

    In the next plugin’s version I’ll add an option on the “WP Admin -> Custom CSS & JS -> Settings” page for removing the comments from the /wp-content/uploads/custom-css-js/* files.

    Plugin Support Diana Burduja

    (@dianaburduja)

    Hello @visualvision,

    you can hide the “previous” button on the last step by adding the following PHP snippet to your website:

    add_filter( "wpmc_hide_last_prev", "__return_true");

    Plugin Support Diana Burduja

    (@dianaburduja)

    I used the “enqueue_block_assets” hook to load the block_css.css
    file in the block editor; however, I overlooked the fact that it would
    also load the file on the front-end.

    I will address this in the upcoming plugin release. Thank you for
    pointing this out.

    Plugin Support Diana Burduja

    (@dianaburduja)

    Hello @guenther999,

    the issue with the red colored text on the red background is unrelated to the Multi-Step Checkout for WooCommerce plugin. That can be easily verified by deactivating the plugin and see that the text turns red when your CSS rule is removed and white when your CSS rule is reapplied.

    The red color originates from the “Link Color” setting found under “WP Admin -> Divi -> Theme Customizer -> General Settings -> Typography”. The individual error messages, like “First Name is mandatory”, are in fact links, therefore they adopt the color defined by the “Link Color” setting in the Divi theme.

    Plugin Support Diana Burduja

    (@dianaburduja)

    Hello @michaelmatzkin,

    I don’t find any plugin called “Insert into Pages”. Do you mean the Insert Pages plugin? If not, then a link to the plugin would be helpful.

    You’re working on the confirmation text for a Gravity Forms form (i.e. “WP Admin -> Forms -> [Your Form] -> Form Settings -> Confirmations”. What confirmation type are you building: Text, Page, or Redirect?

    In the Gravity Forms confirmation text you’ve added a shortcode from “Insert Pages” plugin and within the content of that shortcode you’ve added the [ccj id=”next-entry-semester”] shortcode? Did I understand that correctly? That seems like a very convoluted way of achieving an outcome. Will explain in more detail what are you trying to achieve?

    Will you please create a test page on the website with [ccj id="next-entry-semester"] as content? When viewing that page on the frontend does the shortcode convert correctly to its content? That will test if the “Simple Custom CSS & JS Pro” shortcodes generally work correctly on your website.

    Because the issue is related to the plugin’s pro version, you’re welcome to contact us on the silkypress.com website on the Contact page. This support forum is about issues related to the plugin’s free version. Please answer the above questions in a message posted on the Contact page of silkypress.com website.

    Plugin Support Diana Burduja

    (@dianaburduja)

    The display aspect ratio doesn’t play a role in the zoom effect.

    The WP Image Zoom plugin doesn’t build the <img> HTML element on the website. But the plugin uses the information from the <img> HTML element in order to build the zoom effect.

    The WP Image Zoom plugin by itself doesn’t modify the <img> element.

    The <img> element is generally built by the WordPress core. Some page builders can overtake some aspects of building the <img> element. The theme can dictate what thumbnail sizes should be generated. Sometimes other plugins can also add or remove attributes from the <img> element.

    Again, the display aspect ratio doesn’t play a role in the zoom effect. But it does seem to play a role in adding the full size image URL to the “srcset” attribute of the <img> element. At least on your website, or on this particular image. Which, in turn, affects the zoom effect.

    I cannot debug the reason for which the full size image URL is missing from the “srcset” attribute of the Bonnet Cable <img>. Nor can I debug from the frontend alone why the full size image URL is added to the “srcset” attribute when the display aspect ratio is different. But these things have nothing to do with the WP Image Zoom plugin.

    As a test, you can try deactivating the WP Image Zoom plugin and set the Bonnet Cable image to the same aspect ratio as the full size image. I bet the full size image is still missing from the “srcset” attribute, while on other images on the page it is present. Simply because the <img> element is not modified by the WP Image Zoom plugin.

    Plugin Support Diana Burduja

    (@dianaburduja)

    The zoom effect works when the <img> HTML element links the full size image, or at least the full size image is mentioned in the “srcset” attribute. If the full size image is not present in any of the <img> attributes, then the WP Image Zoom plugin has no information about the full size image and cannot use it in the lens.

    For whatever reasons all the images on the page mention correctly the full size image in the “srcset” attribute, but not the Bonnet Cable image. It also seems to correctly mention the full size image after “change of aspect”.

    Why is the Bonnet Cable <img> element built differently than the other images? I don’t know. My assumption was that there were two images loaded in the Media Library, one full size, another at 150×150 size. If that is not the right answer, then you’re the one with enough information to find out why this quirk with the Bonnet Cable <img> element shows up on your website.

    From my point of view the WP Image Zoom plugin works correctly with the available information in the <img> HTML element and there is nothing to solve.

    Plugin Support Diana Burduja

    (@dianaburduja)

    Hello Josh,

    at the moment I can offer you a rather convoluted solution, which dequeues the scripts added by the plugin, then adds them again on your specific post with another script handle. See this PHP snippet. Replace the is_single( 'simple-post-with-images' ) part with the Conditional Tag matching your post.

    But this gave me the idea to add a filter to the next plugin’s version (which will be released in about 6 weeks) that would conditionally add the scripts only to specific pages. That would be a much better solution.

    Instead of waiting for the next release, you could patch the plugin with this patch (i.e. replace the line prefixed with “-” with the lines prefixed with “+” in the “image-zoooom.php” file), then add the following PHP snippet to your website:

    add_filter( 'wp_image_zoooom_load_scripts', function() {
    return is_single( 'simple-post-with-images' );
    } );

    When updating the plugin to the next version, the patch will be overwritten, but the filter will still work and the scripts will load only on the specific post.

    Plugin Support Diana Burduja

    (@dianaburduja)

    On my side the zoom ratio is very high now on the Bonnet Cable image, both on Firefox and Chrome. It looks like the change solved the issue.

    Or is there another image that has the zero zoom ratio, as it was on the Bonnet Cable image?

    Plugin Support Diana Burduja

    (@dianaburduja)

    Hello @baz74,

    if you open the “WP Admin -> Media -> Library” page, then you’ll find out that the image for the Bonnet Cable was added twice to the Media Library, once in full size (824×893) and a second time in a reduced size (150×150). The image shown on the “Parts” page is the one reduced in size.

    Will you please open the “Parts” page for editing, remove the image for the Bonnet Cable and then add it again, but this time making sure to select the full size version from the Media Library?

    Let me know if that solves the issue.

    Plugin Support Diana Burduja

    (@dianaburduja)

    Hello @samvrgl,

    thank you for reporting the issue..

    I was unable to replicate the error on my test website, despite trying multiple different scenarios.

    Some WordPress hosting companies modify the loading order of resources in order to improve performance and reduce loading times, as part of advanced caching and optimization strategies. It could be that the error shows up under certain conditions related to the modified resource order loading.

    In the 3.51.3 version the wp_rand function call was replaced with the PHP native rand, as per your suggestion, so hopefully that doesn’t trigger the error also under your website’s conditions.

    Plugin Support Diana Burduja

    (@dianaburduja)

    It also needs to lower the z-index of the zoom lens.

    Will you add the following CSS rule:

    .zoomContainer[style] {
    z-index: 40 !important;
    }

    in addition to the

    #tc-page-wrap {
    display: contents;
    }

    CSS rule you’ve already added.

Viewing 15 replies - 1 through 15 (of 41 total)