Forum Replies Created

Viewing 15 replies - 1 through 15 (of 20 total)
  • Thread Starter Erik Ford

    (@wearepixel8)

    Thanks, man. I really appreciate it.

    As soon as I get the plugin update notification, I am all over it!

    Plugin Author Erik Ford

    (@wearepixel8)

    Sorry it wasn’t for you but thanks for the rating. Much appreciated.

    Plugin Author Erik Ford

    (@wearepixel8)

    I am not quite certain I understand what you mean by, “if a portfolio is very long.” Are you referring to your single post view or your archive view?

    If the latter, the plugin will not override your default pagination settings (Reading ? Blog Posts per Page) and will always default to what you have set there. You can override this, in your theme, by setting the posts per page for this custom post type.

    If this is not what you are referring to, could you please elaborate.

    Thanks.

    Thread Starter Erik Ford

    (@wearepixel8)

    So, I have spent the last 24 hours trying to troubleshoot why, after updating to WooCommerce 2.0.1, the cart widget will sporadically display on one page and not the other in our custom theme.

    As I mentioned in my earlier post, I did switch to TwentyTwelve and the cart widget works as expected. Looking at the markup, the only differences were TwentyTwelve uses IDs to wrap content and we do not. In my mind, this would not explain why the widget would sporadically appear but I was willing to give the IDs a shot.

    After doing so, the cart widget did appear and I thought all was right with the world … until I clicked around to other pages that had the widget installed in their sidebar. I quickly discovered that the problem still persisted and the IDs were not the solution.

    The only change with our installation has been the plugin update. So, I decided to download a local copy of class-wc-widget-cart.php to look at the code. I found the comments, on line 71, that indicate that “ … code in woocommerce.js will update [div] on page load … ” which was not happening.

    This lead me to download a local copy of woocommerce.js to inspect that code. Upon doing so, I did not find anything in this file that relates to the cart widget.

    So, I am back here again attempting to find the answer. Can anyone explain what has changed, with this widget, that would cause the behavior we are encountering? If this is not the official support forum for the plugin, can you point me to where I can post my question?

    Thanks.

    Thread Starter Erik Ford

    (@wearepixel8)

    It looks like I spoke too soon. The problem was fixed, momentarily, but resumed once I started clicking other pages within the site. Is there a specific ID I am missing somewhere?

    Thread Starter Erik Ford

    (@wearepixel8)

    Thanks. I found what the issue was by switching to TwentyTwelve. It looks like the plugin is looking for div id="main" which TwentyTwelve uses to wrap the content.

    As a developer, I try to avoid the use of IDs as much as possible but adding the ID to my wrapping div fixes the issue.

    Thread Starter Erik Ford

    (@wearepixel8)

    Thanks. I really would hate to add another HTTP request just for Firefox but will keep your solution top of mind if there are no better solutions.

    Thread Starter Erik Ford

    (@wearepixel8)

    Yup. The minify files are uploading to my CDN which makes this issue even more baffling and frustrating.

    Thread Starter Erik Ford

    (@wearepixel8)

    Yes, I am tinkering with the theme right now. I should be finished by the end of the week.

    In the meantime, this is how I edited your $output string:

    $output = '<div class="fluid_8t" style="position:relative;padding:0;width:100%;padding-top:100%;margin-bottom:1.563em;">';
    $output .= '<iframe class="nd-eight" src="https://8tracks.com/mixes/' . intval($xml->mix->id) . '/player_v3_universal/' . $playops .'" ';
    $output .= 'width="' .intval( $width ) . '" height="' . intval( $height ) . '" style="border: 0px none;width:100%;height:100%;position:absolute;left:0;top:0;"></iframe>';
    $output .= '</div>';

    As you can see, though not wholly optimal, I am using inline styles to make the image responsive. I don’t know if you want to include that in your code or, as I was suggesting, allow themes to filter the $output with something like this:

    // allow plugins to filter the output
    $output = apply_filters( 'eighttracks_shortcode', '', $atts );
    if ( $output != '' ) return $output;

    Just a thought. Still love the plugin though. It has actually gotten me excited about my 8tracks account again.

    Thread Starter Erik Ford

    (@wearepixel8)

    Marking this as resolved. It turns out it was my own fault.

    Erik Ford

    (@wearepixel8)

    We are using Rackspace Cloud Files, for CDN, and the “Host Minified CSS and JS files” option is not available to us.

    under the minify details options

    you need to have “rewrite URL structure” checked

    I checked this option and it is enabled but still unable to use the “Host…” option. Is this related to a step I missed somewhere? Anyone else experiencing this and know of a fix?

    We are 99% there and this is the only problem I am having.

    Thanks in advance.

    Thread Starter Erik Ford

    (@wearepixel8)

    After posting this topic, and looking at my code, I quickly found my mistake. The conditional statement should read:

    <?php if ( ($curauth->user_url ) !='' ) { ?>
    <!-- do something -->
    <?php } ?>

    Thanks. I figured it was something integral to the application itself.

    I would be interested in knowing what can be done to troubleshoot this issue. We are running into the same problem with our Theme Options panel and the custom query in the theme.

    If the category name has an ampersand, the query breaks. I am assuming that this is because it is interpreting the ampersand as code. So, how do we get the data from the Theme Options and convert it into something that won’t break the query?

    Thread Starter Erik Ford

    (@wearepixel8)

    I was completely over thinking this one and found a solution with the get_post method.

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