WebmistressM

Thank you, that would be appreciated to make that consideration.

Would it be safe to say that, adding on my Google fonts* into my child theme just by simple CSS calls and loading it in functions.php? (Reference to what I mean in detail, covered in this older tutorial: https://wpsmackdown.com/google-fonts-wordpress/#google-font-face)

* whether self-hosted or hosted with Google. I dont mind self-hosting the fonts

@jdembowski No problem. Didnt mean to double post. Form error

Hello,

I ran into this as well where sort order was not taking. I would go into Sort Gallery and make changes in the order. When I pressed save and the screen refreshed, the order went back to the way it was before I changed it. No matter what, I could not get this to take.

At first I thought maybe it was a problem with NextGEN itself. However, when I disabled NEXTCellent Gallery and tried to change the sort order with NEXTGen enabled, the issues of sort order did not present itself any longer. So, I began a search on NextCellent to see if it was the culprit. Sure enough…

https://www.ads-software.com/support/topic/sort-function-is-missing

If you go down and view niknetniko’s responses, you will find that Alex Rabe (the developer of NextCellent) has issued a fix for this. Thank goodness!

M. Watson

Thanks niknetniko,

Your fix solves my problem completely. I was pulling out my hair wondering what was wrong with my site.

Oop, spoke too soon. With the current release of 1.5.7.2, Im still finding that there is no way to restrict a widget’s display between tablets and smartphones.

In the device setting (for my slideshow widget), I can only check these boxes.

[ ] Desktop
[ ] Mobile

Just like WordPress’ wp_is_mobile function, it defines mobile device as any sort of touch device. So, Im still unable to specifically target smartphones as the one to hide this widget but allow tablets to still use it.

Is the next rendition of your beta able to differentiate tablets from smartphones? Is this even possible?

Sadly, none of the suggestions above work for me. Im not having the issues (others here have described) regarding responsiveness in mobile view. However, I am having the issues when it comes to centering the images that appear in the slideshow, due to some images being landscape and others being portrait.

Firebug did allow me to test if I could add margin-left: auto and margin-right auto to the inline css its pulling out. However, I have no clue how/where I would add that in. The jquery that niknetniko gave didnt seem to have any effect.

Here is what I get inline on the slideshow, and where I can add the margin auto declarations in Firebug to get the centering I am seeking.

‘element {
height: 155px;
position: absolute;
z-index: 6;
top: 0px;
left: 0px;
display: none;
width: 116px;
opacity: 0;’

Definitely looking to create a “replacement” widget that only shows up in mobile sites. The replacement it will do is for a widget that I have hidden from mobile view because it uses alot of data and therefore would be inconsiderate for those accessing via their mobile provider’s data plan.

The 1.5.7.2 version seems to do the trick but definitely dont want to roll that out on a live site. Any ETA on when the “mobile only” changes might be released officially?

I have run into this as well, starting maybe yesterday or the day before. Error message is the same:

There seems to be an error reaching the WooThemes API at this time. Please try again later. Should this error persist, please log a ticket in our help desk.

I am gathering that 5.6 came out and my current WooTheme is 5.5.3. Not sure if I should wait it out or try and upgrade manually

I actually would like to know this as well. I see a place to put in a SKU (and it can be disabled/enabled within WooCommerce’s settings).However, there is no place to put a UPC code. Any idea if we can do this beyond using core’s custom fields?

@fireproofsocks

Thanks so much. I had originally thought of doing things this way but didnt know if the summarize posts (which has seen significant improvement since when I first started this project) was the more updated solution. I guess it was inevitable that I would do things through get_posts in a template file because I do need to filter the list a bit. Basically Im going to need the equivalent of an if/then/else statement so that the get posts filters out any of my custom post entries which have either of the 3 checkboxes (from a multi select custom field) checked.

Oh this is very helpful for figuring out how to get real specific. I need to control this list quite a bit more than I think is sane but Im trying to single out some and then place them back into another list element below the first array.

So where would these $arg = array () go? , a template page that I call within that page?

In the case that this is accessed later, I have put this in as a feature request for now:

https://code.google.com/p/wordpress-custom-content-type-manager/issues/detail?id=477

Its based off of Reverie in the respect that i copied /themes/reverie into themes/kybtheme. Thats the thing I wanted to make clear since creating a child theme would imply a slightly different process vs making a “sister theme”/clone of reverie.

Makes perfect sense, actually. Incidentally, this seems to make the need for Summarize Posts plugin obsolete, as I was only trying that plugin for this issue in the first place.

Okay… hopefully Im not breaching protocol by doing this, but it looks like one of the most recent CCTM upates “killed” the solution that worked so well up there.

Part of the problem is with the Summarize Posts plugin as fireproofsocks is working on integrating the two plugins as one. So, there is a conflicting class between the 2 plugins.

Issue described here: https://code.google.com/p/wordpress-custom-content-type-manager/issues/detail?id=300

For now, all I can do is disable the Summarize Posts plugin. However, this has produced issues with the following code:

<?php
 $results = get_posts(array('post_type'=>'order_queue'));

foreach($results as $r) {
        $r = get_post_complete($r->ID);
        echo "<br />";
        print $r->ordernumber;
        echo "<br />";
        echo "<span>";
        print $r->order_status;
        print $r->itemETC;
        echo "<br />";
}
 endwhile; // end of the loop. ?>

probably due to me having to disable Summarize Posts while integration is completed.

Until then, the result on my lising page (lsting_orderqueue.php) is Notice: Trying to get property of non-object… Any coding that I might do in the meantime?