Forum Replies Created

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

    (@redpixelstudios)

    Are you still experiencing this issue? We noticed that you posted a wish list for the plugin and thought that might indicate that you got it working. If not, we would recommend disabling all other plugins and trying again. If the problem persists then it is an issue where we would need to know more about your WordPress install. If not, then there is a plugin conflict that will need to be isolated by activating one after another while testing the sitemap generation each time.

    Plugin Author redpixelstudios

    (@redpixelstudios)

    You are quite welcome. We strive to make excellent plugins and have the WordPress community to thank for their invaluable feedback and testing. All the best.

    Plugin Author redpixelstudios

    (@redpixelstudios)

    You are quite welcome.

    We looked at the differences between version 1.0.7 and 1.0.9 to see what could be causing the issue. We were unable to locate any significant change in the method used to retrieve the content that would cause the issue that you described.

    As you are likely aware, any shortcodes within the content are executed before it is included on another page, but the scope of what is retrieved is limited to $post->post_content or $post->post_excerpt, depending on the shortcode “content” argument.

    We did replace the wpautop function that was being run on the content with “the_content” filter, but that does not seem to be the culprit.

    If it is not too much trouble, could you disable all plugins except RPS Include Content 1.0.9, update the page containing the rps-include shortcode and see if the problem persists? If it works you would just need to activate plugins until you find the conflict. Let us know.

    Plugin Author redpixelstudios

    (@redpixelstudios)

    No problem Brett. RPS Image Gallery is a class, so you need to access its methods (functions) slightly differently. In order to get the Gallery Link URL for a specific attachment, you would need to use:

    $full_image_url = RPS_Image_Gallery::get_gallery_link( $attachment->ID );

    You can do something similar to access the target by calling its method like so:

    $full_image_url_target = RPS_Image_Gallery::get_gallery_link_target( $attachment->ID );

    Of course you can echo the result or set the variable names to whatever you wish. We hope that this addresses your question. Let us know how it works out for you. Thanks for using RPS Image Gallery.

    Plugin Author redpixelstudios

    (@redpixelstudios)

    rosedai,

    Please consider opening a new thread with your request since it doesn’t seem to fit within this discuss. Also provide a link to a specific example of the issue along with details regarding how to replicate the problem. Thanks in advance.

    Plugin Author redpixelstudios

    (@redpixelstudios)

    ernymiles,

    Just to clarify, the margins are being set using CSS attributes. Without styles, the gallery displays as an unordered list rather than a series of inline-block elements. It appears that you were successful in overriding the width of the list items in your 8 column layout.

    Based on our review the widths of the list items are specified properly, according to CSS specifications, though we have rounded the values to the next lowest whole number. It seems that no matter what precision value we use in rounding, there could be sizing issues because of three factors:

    1. the container width of the gallery is an unknown
      • browsers handle rounding differently
      • CSS does not specify a certain precision for floating point numbers

    To help explain, let’s take the example that you provided of the 8 column layout. You are correct that the width of each column would be 12.5%.

    100% / 8 columns = 12.5% per column

    Now let’s assume that the container width is 630 pixels. Each of the columns will be 78.75 pixels wide.

    630 pixels * .125 = 78.75 pixels

    Since browsers cannot render 75 hundredths of a pixel, they will round up or down, depending on their programmed behavior. In the case of rounding up, the width of the columns would exceed the container by 2 pixels.

    79 pixels * 8 columns = 632 pixels

    In the case of rounding down, you would come up short of the container width by 6 pixels.

    78 pixels * 8 columns = 624 pixels

    You could easily address this by adjusting the width of your container so that the column width calculation would result in an integer. Though that might affect your overall page layout.

    As you can see, there is no easy answer to this issue, and no right or wrong, just a series of hardware and software constraints that we must understand to address display issues on a case by case basis. In our opinion, overriding the included CSS (which we consider a starting point) still remains to be your best bet. That being said, adjusting the CSS that is bundled with RPS Image Gallery so that floating point percentages are used is being discussed and considered. If implemented, the list item widths (and resulting row widths) would be:

    9 columns = 11.11%  (99.99%)
    8 columns = 12.5% (100%)
    7 columns = 14.285% (99.99%)
    6 columns = 16.666% (99.99%)
    5 columns = 20% (100%)
    4 columns = 25% (100%)
    3 columns = 33.33% (99.99%)
    2 columns = 50% (100%)
    1 column = 100% (100%)

    We hope and believe that this explanation and proposed modification should bring this thread to a close. Should you require additional information, please consider reviewing the following:

    Plugin Author redpixelstudios

    (@redpixelstudios)

    We are pleased that RPS Include Content is working out for you. In order to support password protected posts, we had to make some modifications to the plugin, and in doing so have released version 1.0.9. Let us know if you have any troubles with the modification and we will do our best to get them addressed.

    Plugin Author redpixelstudios

    (@redpixelstudios)

    We are pleased to announce that RPS Image Gallery version 1.2.9 (released today) has the functionality you requested. Please let us know how it works for you or if there are any questions or issues. We would be interested in your appraisal of the instructions for implementing the new feature. Thanks in advance for your time.

    Plugin Author redpixelstudios

    (@redpixelstudios)

    You can certainly override the CSS that specifies the margins. The default margins are set to 5% of the container width, so setting them to a lower value should allow you achieve the desired effect.

    Plugin Author redpixelstudios

    (@redpixelstudios)

    One of the arguments available for the shortcode is “size_large”. It allows you to specify the image size to be used in the slideshow by referencing the image size name (i.e. medium, large, full). However, it does not accept pixel dimensions in the current release.

    Probably the best solution would be to add a custom image size to your theme’s functions.php file by using the add_image_size function. If you give that custom size the name “slideshow”, then you would reference it like so in the gallery shortcode:

    [gallery size_large=slideshow]

    You will likely need to regenerate image thumbnails after adding your custom sized image in order for it to be available when called. The Regenerate Thumbnails plugin by Viper007Bond makes this a trivial task.

    Another option is for you to redefine the Large size image dimensions in your WordPress Media Settings to be 1500 (max width) by 1500 (max height). Of course you can set the height to some unlikely value such as 99999 so that even vertical oriented images will be 1500 pixels wide.

    Let us know if you have any further questions or if this solves the issue. Thanks.

    Plugin Author redpixelstudios

    (@redpixelstudios)

    Thanks for posting your solution to the issue and for using RPS Image Gallery.

    Plugin Author redpixelstudios

    (@redpixelstudios)

    We hope that the issue has been addressed and are marking this topic as resolved. Please let us know if more information is required.

    Plugin Author redpixelstudios

    (@redpixelstudios)

    We should be able to help you out there. You would need to setup a Google Webmaster Tools account and register your sitemaps for each domain. In addition, you can specify the location of your sitemap in the robots.txt file like so:

    Sitemap: http://www.example.com/sitemap83.xml

    That way you wouldn’t necessarily need to register with other search engines to submit your sitemaps for them to be discovered. We hope that this information is what you needed.

    Plugin Author redpixelstudios

    (@redpixelstudios)

    You are correct that this is not a current feature of RPS Image Gallery though it sounds like a worthwhile addition to the plugin. We have added it as a feature request for the next release. Thank you for taking the time to write and providing such a thorough description.

    Plugin Author redpixelstudios

    (@redpixelstudios)

    It seems that the result would be similar whether using percentages or floating point numbers considering that the container width is an unknown and the browser rounds pixel measurements to an integer. Please feel free to share if you have information or an example that would help illustrate your point.

Viewing 15 replies - 376 through 390 (of 420 total)