Forum Replies Created

Viewing 15 replies - 1 through 15 (of 420 total)
  • Plugin Author redpixelstudios

    (@redpixelstudios)

    If you’re interested in having us look at the issue with RPS Image Gallery on your site, please feel free to open a support thread.

    Plugin Author redpixelstudios

    (@redpixelstudios)

    Digging into it a bit further, it seems the HTML is not complete. When inspecting the page source, the very last line is:
    <div id="credits">Powered by <a href="http://wordpress.org/"><strong>WordPress</strong></a> | | Thanks to
    Something is preventing the HTML output after the “Thanks to”. We hope that helps you to isolate which plugin might be causing the issue. Let us know if you need further help.

    Plugin Author redpixelstudios

    (@redpixelstudios)

    There are no JavaScript errors that are usually the cause of such problems. It looks like both http://www.detske-casopisy.cz/kliceni-2/ and http://www.detske-casopisy.cz/error/ are running on the same install of WordPress with the same theme and same version of RPS Image Gallery. If that is the case, then the issue might be with something else that is loading on the error page that is not loading on the page that is working. Perhaps try emptying your cache or disabling the SuperCache plugin to see if that helps.

    Plugin Author redpixelstudios

    (@redpixelstudios)

    Please send along a URL showing the malfunction and we’ll do our best to assist.

    Plugin Author redpixelstudios

    (@redpixelstudios)

    Adding the “group_name” attribute to the gallery shortcode should allow you to achieve your objective. Just be sure each gallery has a unique group name and you should be fine. The default group name is “rps-image-group” so instead you might have “group-1”, “group-2” and so on. Let us know how it works out for you.

    You can hide the all jobs link by adding a bit of CSS to your theme.

    //hides the "Go to all jobs" link at the bottom of Indeed pages
    a[href$="indeed-jobs/"] {
        display: none;
    }
    Plugin Author redpixelstudios

    (@redpixelstudios)

    We should be able to help you out. What is the gallery short code in use on the page in question?

    Plugin Author redpixelstudios

    (@redpixelstudios)

    If the post where the injected content is being displayed is utilizing the_content filter, you might need to disable filtering within the rps-include shortcode. It is also possible you might find a different way to achieve the desired result with a simpler configuration. Introduction of a page builder does add complications that you don’t have with the default WordPress content editor.

    Plugin Author redpixelstudios

    (@redpixelstudios)

    You have quite a few variables at play here. If possible, run the following updates in order on the WP 4.7.7 install (sandbox preferably), testing the results after each update:

    1. RPS Include Content 1.1.8 -> 1.1.10
    2. WordPress 4.7.7 -> 4.9
    3. Enfold 4.0.2 -> 4.2
    4. Add Caldera forms and a sample form to the included content

    That should give you and us more to go on.

    Plugin Author redpixelstudios

    (@redpixelstudios)

    Thanks for the thorough description of the issue. We believe that we have addressed the issue with a new version (1.1.10).

    A new shortcode attribute has been added to allow the processing of embeds. It has been set to not process embeds by default to avoid any display issues on sites that are currently using RPS Include Content. It should look something like this:

    [rps-include blog="30" page="18098" filter="true" embeds="true"]

    We have done preliminary testing but would appreciate it if you could try the new version to make certain it meets your expectations. You may download it from the wordpress.org repository.

    Once we receive confirmation from you, we will go ahead and release the version to the general public. Thanks in advance.

    Plugin Author redpixelstudios

    (@redpixelstudios)

    It appears there is a JavaScript error on the page located at line 95 character 23.

    TypeError: $ is not a function: var $active = $(‘#slideshow a.active’);

    Deleting the offending script removes the error and allows other JavaScript to function including the version of Fancybox that ships with RPS Image Gallery.

    We are not sure where the offending script originates, whether it is part of another plugin or the theme you are using. Recent updates to other plugins or your theme might provide a clue.

    Plugin Author redpixelstudios

    (@redpixelstudios)

    We understand the layout challenge you are facing but think there may be a more flexible solution.

    Truncating the caption by word or character count may or may not yield equal height rows depending on the fonts used and the letters comprising the caption. The solution also doesn’t provide equal height enforcement regardless of viewport width.

    We suggest a CSS/JavaScript solution instead. In fact, you may be able to apply RPS Image Gallery settings to achieve the desired result. The masonry option can display elements with various heights in an optimal way. Or, you might consider locking the height of the caption and adding a gradient overlay to make the caption fade off. You could even disable the caption entirely in the gallery view and just have it display in the slideshow view.

    Hope you find this information helpful. Let us know if you have further questions.

    Cheers

    Plugin Author redpixelstudios

    (@redpixelstudios)

    There should be nothing preventing the usage of custom post types, unless the post type is not public. RPS Include Content uses get_blog_post and get_post, so it is only subject to the constraints of those functions.

    Just to confirm, we tested the scenario by creating a custom post type, adding a post of that type and including it on a page. Perhaps there is some restriction that is preventing the post from being returned when accessed by get_blog_post or get_post.

    Plugin Author redpixelstudios

    (@redpixelstudios)

    It sounds like the permissions which allow or deny file creation may have changed since before the creation of the third site. Would you or your hosting provider be able to check the permissions to make certain WordPress has write permissions to the directory where the sitemaps are located?

    Plugin Author redpixelstudios

    (@redpixelstudios)

    Normally we would suggest that you simply disable the plugin associated with the conflicting script or deregister it. However, the script seems to be part of the theme and doesn’t appear to be registered using conventional methods. So your best recourse is to ask the question of your theme developer. They may be able to point you to a specific setting or method to disable prettyphoto.

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