Forum Replies Created

Viewing 11 replies - 1 through 11 (of 11 total)
  • Unfortunately you have to do this for each and every site. We have 2 cloud server products and SG requires us to delist each new site we add, but then they always tell us in the ticket they can’t do it. Once we insist they do it, but it’s quite the hassle.

    We manage updates for our users by performing the updates on staging sites before hand and we usually delay a week or two from a major release as there’s almost always breaking bugs and immediate patches. While I appreciate the need for updates when SG updates sites, if something breaks we then have to fix it, often as unbillable time.

    If anyone asked me what I thought about SG I’d say their services is good, their support is good, but unless you’re committed to being available to repair the site at the drop of a hat after they push potentially site breaking updates you may want to see what other options you have. I don’t know if I could run anything mission critical on such a system.

    I’m having the same issue and sad to see there’s no response. Selecting a list is not working on GF 1.9.17.5 and addon version 3.0

    If you’ve enabled a custom sidebar on a post/page you’ll see a new sidebar with the format pps-{slug} where slug is from the page you enabled custom sidebars for.

    I don’t have a menu option like that either, I think it’s old documentation. Look in your widgets page.

    The ‘unexpected end’ error can be misleading with the line number, it can only determine where it became certain the brackets weren’t open/closed correctly. The error has to be above that line, as posted the 2nd add_meta_box function call would not be conditional. This would likely work it would just add the metabox to users who can’t otherwise “edit_theme_options”, but I would still bet on it missing from code above that line.

    Todd, thanks for the info but I’m not sure you’re correction has it right. There should definately be an opening bracket at the end of the line beginning with ‘if’. There may be a missing closing bracket above that line though.

    By default it doesn’t seem to show the count if the count is 0.

    Posted too soon, it was working fine I just had the wrong sidebar to replace selected. So all I did was:

    in: pps_reg_custom_sidebar():
    if ( is_page() ) {
    to
    if ( is_page() || is_single() ) {

    in: pps_save_postdata():
    if ((‘page’ == $_POST[‘post_type’] ) and current_user_can(‘edit_theme_options’)) {
    to
    if ((‘page’ == $_POST[‘post_type’] || ‘post’ == $_POST[‘post_type’] ) and current_user_can(‘edit_theme_options’)) {

    and in: pps_add_custom_box():
    if ( current_user_can(‘edit_theme_options’) ) {
    add_meta_box(‘pps_sectionid’, __( ‘Custom Sidebar’, ‘tcc_pps_domain’ ), ‘pps_inner_custom_box’, ‘page’, ‘advanced’, ‘high’ );
    }

    to:

    if ( current_user_can(‘edit_theme_options’) ) {
    add_meta_box(‘pps_sectionid’, __( ‘Custom Sidebar’, ‘tcc_pps_domain’ ), ‘pps_inner_custom_box’, ‘page’, ‘advanced’, ‘high’ );
    add_meta_box(‘pps_sectionid’, __( ‘Custom Sidebar’, ‘tcc_pps_domain’ ), ‘pps_inner_custom_box’, ‘post’, ‘advanced’, ‘high’ );
    }

    Not sure if that helps anyone. Neat plugin, I just finished a site which had a different plugin per page. Couldn’t find this at first and was going to try and write one that integrated the widget editor on the post page itself, but this is SO much easier and less prone to fault.

    Also agree. I’ve tried adding the functionality myself, I enabled the meta box to appear on posts. It’s saving that data, the new sidebar shows up in the widgets page. For some reason it’s still showing the default sidebar, but I’m sure I’m missing something small. “Official” support for this would be nicer.

    Fair enough. It may be worth adding that to the notes as a possible way to ‘enable’ My Link Order for widgets. In my case I had the widgets in place when the site owner told me they wanted to order the blogroll, so in my specific case it’s much easier to filter the arguments.

    It could also be a plugin setting, left off by default for legacy purposes.

    I find it odd that you have to use a custom widget. Why not utilize the links widget’s arguement filter as such:

    add_filter(‘widget_links_args’, ‘enable_link_ordering’);
    function enable_link_ordering($args)
    {
    $args[‘orderby’] = ‘order’;
    $args[‘category_orderby’] = ‘order’;

    return $args;
    }

Viewing 11 replies - 1 through 11 (of 11 total)