[terrysmith]

There is a global catalog mode but individual products with an empty price should be in “catalog mode” as well. You can google this to verify.

The product that I was referring to does not have variations.

I created a new product and set nothing on it but the name and assigned a category (the price is empty by default) and the New badge displays. What did you do in your test to make the New badge disappear so you could test the Free badge?

I’m currently testing this functionality because half of my website will be for sale items and half will be catalog items, and I need to ensure that it will all work. So far it looks like the buy button and price are hidden everywhere they need to be on the catalog items.

 

 

 

 

 

[terrysmith]

Thanks. I’ll look at that setting, but what do you mean by “quality” of the images? You have that in your documentation too and it’s completely meaningless to me if you’re not using those image sizes. Quality to me is image size and the JPEG compression setting.

[terrysmith]

I’m mostly there with this code. I think I can add a tab as well.

add_action( ‘woocommerce_product_meta_start’, “ACF_product_meta_content”, 10 );

function ACF_product_meta_content() {
if (get_field(‘dimensions’))
{
echo the_field(‘dimensions’);
}
}

Unfortunately, the SKU and Category meta are not being output in structured HTML that is easy to style and match to:

<span class=”sku_wrapper”>SKU: <span class=”sku” itemprop=”sku”>TestProduct</span>.</span>

Is there an easy way to override the meta output completely?

 

[terrysmith]

That worked. Thank you!

[terrysmith]

Thank you for your help Ed, and double thank you for changing the second H1. I’ve overridden the sf_post_info() function and that’s getting me closer to what I need. I still have some work to do on it. The remove action for related articles is still not working though. I also turned off related articles for a post in its meta options and that didn’t work either. What am I missing?

Just so you know my goal is to turn off related articles and replaced it with the short-code for the Contextual Related Posts plug-in and then customize that further.

Thank you,
Terry

[terrysmith]

Thank you for fixing the esc_attr() in the next update. The video is referring to multiple, logical H1 sections on a page, not two H1’s with identical wording at the top of the same section. Google may not penalize for that currently, but it looks like keyword spamming and is bad structure regardless.

Can you or someone else please address my other questions?

Thanks,
Terry

[terrysmith]

This reply has been marked as private.

[terrysmith]

I have copied sf-post-detail.php to my child theme, in the same folder structure, and set the following after the variables have been set by the standard code:

$show_author_info = false;
$show_related = false;

Some posts are still displaying these sections and some are not. What am I missing?

Thanks,
Terry

[terrysmith]

Thanks Ed,

I added the remove_action line to functions.php in my child theme, but the related articles are still displaying. Am I missing something?

Terry

[terrysmith]

Hi Ed,

I have saved the permalinks many times trying many different combinations. I believe there are multiple problems and that the theme is involved because the blog index is not a page builder page and not a typical blog page. (For example, the note in your documentation not to set the page as the “Posts page” in “Reading Settings”.)

However, just to start with, I have a Category base of “journal” set and none of the main menu links or sidebar links for categories are reflecting this. I’ve tried different base names, save the menus again, removed/added menu category items, etc.

Terry

[terrysmith]

I just discovered that it happens when you active a child theme of Aetlier as well, so now I can’t customize the theme until this is fixed.

[terrysmith]

Thank you Ed,

I’m glad to hear that you don’t think this should be by design.

There was no error message. In this scenario the website and admin area are both completely blank. I looked at the source and want to say, though I don’t remember with 100% certainty, the source was empty too. Somehow a good response code was returned from the server but with no HTML? I was using Chrome by the way. I renamed the plug-in as a total guess, and it worked. Any of users who don’t have server access, at least immediately, would be very stuck!

It should be very easy to reproduce, just switch an Atelier site to Neighborhood without disabling the plugin first.

Thank you,
Terry

[terrysmith]

Let me understand this… You have 6,000+ sales of Neighborhood and 300+ of Atelier. You’ve just decided to not make big enhancements to Neighborhood which was your flagship eCommerce theme but instead create an entirely new one. Then, instead of making it easy to migrate every last setting that could possibly be migrated so that your converted customers would only have to setup new functionality, you decided, no, screw them, they can just do everything from scratch again. Logos, fonts, colors, blog settings… it doesn’t matter if it’s obviously in both themes they can just do all of the work again.

Not only that, but when your customers try to switch back to Neighborhood to see what some of their settings were they get a completely blank website and admin area due to your new plugin. (See http://www.swiftideas.com/forums/topic/everything-blank-after-switching-back-to-neighborhood-theme/#post-172660) But that’s OK too because, according to the other post, it’s by design!

[terrysmith]

Are you joking? Your plugin should never, under any circumstances, cause someone’s whole website and whole admin area to become completely blank and completely unreachable. It is not “by design” or acceptable.

If that means the plugin needs to read the DB, see what theme is active, and not do ANYTHING if it’s not one of your supported themes then that is what it needs to do! Is that really hard to understand?

[terrysmith]

Also…

What is the list of features that are in Atelier which are not in Neighborhood? Most importantly for all of your Neighborhood customers, what does Atelier NOT do that Neighborhood does? Where are these lists?

I hope you can understand that since, to my knowledge, none of the above has been published anywhere is really a total “crap shot” for someone like myself to buy your theme, install it, and see what might still work and what doesn’t. With a blog that’s not too hard. With an eCommerce store there’s a lot more to it.

Terry