Forum Replies Created

Viewing 15 replies - 181 through 195 (of 332 total)
  • Plugin Contributor Matt Cohen

    (@mattyza)

    Hi there,

    There is a conflict with your theme’s CSS styles. πŸ™‚

    The “.fade” CSS class in your theme has an opacity of 0.

    You can force this to be visible by using the following CSS:

    .testimonials .fade { opacity: 1 !important; }

    Regards,
    Matty.

    Plugin Contributor Matt Cohen

    (@mattyza)

    Hi there,

    A new taxonomy, specific to testimonials, has been added in version 1.3.0. πŸ™‚

    Thanks and regards,
    Matty.

    Plugin Contributor Matt Cohen

    (@mattyza)

    Hi boodaddy,

    Thanks for your query. πŸ™‚

    If you can see the output when you copy/paste the HTML, then there is a styling conflict within your theme or another plugin’s CSS (at the time of writing, the testimonials plugin doesn’t output any CSS).

    I’d advise checking the “display”, “visibility” and “height” properties.

    This can be done using “Inspect Element” in Google Chrome/Safari or the “Firebug” extension in Firefox.

    Regards,
    Matty.

    Plugin Contributor Matt Cohen

    (@mattyza)

    HI GrΓ©goire,

    Thanks for your query. πŸ™‚

    Have you setup the conditions under the “WooCommerce” tab when creating your widget area?

    Regards,
    Matty.

    Plugin Contributor Matt Cohen

    (@mattyza)

    Marking as “resolved” until more information/screenshot can be provided.

    Plugin Contributor Matt Cohen

    (@mattyza)

    HI TheNightRider,

    Please see my responses below:

    1. Yes, that’s correct. The use case we found is when “Editor” users logged in, they could see the “Widget Areas” menu yet, when clicking the link, the got a notice saying they didn’t have permission to be there.

    2. This is something that is restricted on a per-role basis only at this stage. πŸ™‚

    Regards,
    Matty.

    Plugin Contributor Matt Cohen

    (@mattyza)

    Hi TheNightRider,

    No problem. πŸ™‚

    This means that, instead of the “Widget Areas” menu displaying for users who have the “switch_themes” capability, it is displayed for users who have a role that has the “edit_theme_options” capability.

    This avoids scenarios where the menu item is displayed for users who cannot add widget areas.

    This was an edge case, and most users of WooSidebars shouldn’t be affected by this. πŸ™‚

    I hope this clarifies your query. If not, please let me know. πŸ™‚

    Thanks and regards,
    Matty.

    Plugin Contributor Matt Cohen

    (@mattyza)

    Hi Syrehn,

    Thanks for your query. πŸ™‚

    This is, unfortunately, a limitation due to the design of the list tables in WordPress core and that they scale poorly when scaling horizontally.

    The best course of action here would be to minimize the number of columns in use. This can be done under the “Screen Options” tab in the top-right corner.

    We’ll explore changing that text into an icon in a future version of the plugin, if we feel it would benefit the plugin. πŸ™‚

    Thanks and regards,
    Matty.

    Plugin Contributor Matt Cohen

    (@mattyza)

    Hi Elmarie,

    Thanks for your query. πŸ™‚

    I believe the slug of your sidebar wasn’t set correctly when it was created.

    Please click “Quick Edit” for the custom widget area that’s causing the issue, type in a slug that is similar to your widget area title (for example, of the title is “Custom Widget Area”, the slug should be “custom-widget-area”).

    This should resolve the issue when you add widgets to this sidebar going forward. πŸ™‚

    Thanks and regards,
    Matty.

    Plugin Contributor Matt Cohen

    (@mattyza)

    Hi Jason,

    I’d advise either removing the folder manually and replacing it via FTP, or removing the folder manually via FTP and then re-downloading directly from the “Plugins -> Add New” screen within WordPress.

    Thanks and regards,
    Matty.

    Plugin Contributor Matt Cohen

    (@mattyza)

    Hi sorensenss,

    This is possible, yes.

    Please place the following code to your theme’s “functions.php” file or in a custom plugin:

    add_post_type_support( 'yourposttypehere', 'woosidebars' );

    This enables a new tab for posts of the specified post type, a checkmark on the post type’s “list” view (for enabling specific entries to have WooSidebars support) and conditions for all posts of that type. πŸ™‚

    Regards,
    Matty.

    Plugin Contributor Matt Cohen

    (@mattyza)

    Hi amommy,

    WooSidebars doesn’t currently support “all posts with a specified tag” conditions, unfortunately.

    I’ve logged this as a possible future enhancement in GitHub here: https://github.com/woothemes/woosidebars/issues/2

    Plugin Contributor Matt Cohen

    (@mattyza)

    Hi markymark2007,

    For your default homepage, please use the “Template Hierarchy > Default “Your Latest Posts” Screen” condition. πŸ™‚

    Plugin Contributor Matt Cohen

    (@mattyza)

    Hi BillyRyan,

    Thanks for your query. πŸ™‚

    For future reference, please create new forum posts for new queries.

    “per_row” can be set on the shortcode. For example, per_row="3".

    I hope this clarifies your query. If not, please let me know. πŸ™‚

    Plugin Contributor Matt Cohen

    (@mattyza)

    Nevertheless, while “get_header()” isn’t strictly required, as it doesn’t inhibit a theme from being a theme (and this is left to the discretion of the theme developer), it is important when making decisions of this nature to consider the implications there-of, such as removing a widely-used hook (ie: accounting for it with the appropriate do_action() call, as you’ve done in your recent commit).

    Thanks for checking in and responding on this thread. I’m glad the issue has been resolved. πŸ™‚

Viewing 15 replies - 181 through 195 (of 332 total)