stl99

Hi there,

Thanks for the feedback. New images are created just fine, only old ones are missing. I switched servers recently, I’ll investigate if some non-WP files haven’t been moved.

Is there a way to use the actual WP featured image instead of WPP-created ones?

Cheers,
Thomas

Hi there,

All good, sry for the confusion!

Cheers,
Thomas

Hi there,

The proofreading settings page offers a field for adding terms that should be ignored. Currently, you have to add or remove each one of them manually.

When you start a new site and want to add your personal “proofreading archive” you can’t import the items that should be ignored from another site/installation.

Does that clarify things?

Cheers,
Thomas

Mainly, I need the separate fields for administrative purposes. Maybe I do use only one bulk block after all though.

Anyway, thanks für the feedback!

Cheers,
Thomas

Thanks for the quick reply!

It would be great if in addition to the “Products tab description” field other text fields could be added. These, if filled with content, should be displayed below the description field content.

I’m thinking of additional contact information or links inside unique fields, not just one bulk-info block. That way, something like an about page for a brand would only have to be created/maintained once.

Basically additional term meta fields for the attribute info tab.

Cheers,
Thomas

Hallo,

ja – leider liegen die Gr??en genau zwischen denen, die wir für verschiedne ?hnliche Designelemente nutzen.

VG
Thomas

Thanks for letting me know!

Cheers,
Thomas

Hi there,

Works now, thanks!

Cheers,
Thomas

Hi there,

No, I directly embed Facebook, YouTube, Twitter, Instagram, etc. URLs/embed code into the post. This works fine with URLs/links that are supported by AMP. Older embeds or the YouTube shortlinks aren’t automatically converted though.

So I’m wondering if I really have to replace all old embeds (with the direct links/URls) for AMP?

Cheers,
Thomas

Thanks for the input. I suggested this as official feature on github.

Make/model – or any brand/product relationship – should be displayed in one select in a hierarchical structure in my opinion. Often there’re rather complex product “trees”, especially when it comes to accessories, vehicle parts etc.

Cheers,
Thomas

I finally got it, thanks!

Cheers,
Thomas

OK, thanks for the heads up! So I guess this year it will keep working all right then.

Frontend management of products via third-party forms/plugins is probably not your main concern. It would be great if product attributes would “just work” with taxonomy terms no matter how or where they have been added or changed though.

Over the years frontend management will most likely become way more important than it is now. This would be a key feature for WooCommerce to function as a comprehensive solution for user marketplace projects (like ebay, etsy etc..).

Cheers,
Thomas

Hi there,

Thanks. I hired a developer that helped me out with this. It was rather tricky to make the WooCommerce product meta box attribute section syncing its taxonomy terms reliably when using WP, Woo as well as a frontend form for updating products…

Any plans to change how the product attributes creation/saving via the Woo product meta box works anytime soon?

Cheers,
Thomas

OK, thanks. But for some reason taxonomy terms that are created externally – e.g. via a form plugin – aren’t “synced” with the Woo product meta box attribute section either.

They’re definitely there and set in the corresponding WP taxonomy though. It seems there’s an extra step necessary to get taxonomy term as attributes in the Woo product meta box (while custom product fields work just fine via woocommerce_process_product_meta).

Maybe there’s a hook to let the Woo product meta attribute section fetch/save all terms regardless of if they have actually been added via the Woo meta box…?

Would it be OK for you if I contact you via your website’s contact form?

Cheers,
Thomas