Rimas
Forum Replies Created
-
Ugh, my reply with links to XML examples has been held for moderation for over an hour and a half now.
Hi @monircoderex, and thanks for your response!
The two marketplaces in question don’t seem to be supported by your plugin at the moment, which is no wonder since they are both regional players only.
One of them is varle.lt, here’s their example annotated XML file (they also have one in Lithuanian, since it’s where they operate).
The other one is pigu.lt/220.lv/kaup24.ee/hobbyhall.fi. They support four different XML file structures: two for products and two for stocks and prices. The products ones not only have nested elements, but are also multilingual by design, and one of the two stocks and prices XMLs allows specifying this data per-country for the four countries they operate in. They provide the following PDF specifications for the XML formats they accept:
The second marketplace also provides a separate plugin for WooCommerce which generates the XML files. I would gladly remove that plugin from our installation though in favor of Product Feed Manager.
So, followup questions:
- Feature request: please make it possible to specify nested paths for custom attributes. For example, a custom attribute with name
foo.bar.bazorfoo/bar/bazcould mean that I need the field in an XML elementbazwrapped bybarwrapped byfoo. This would empower easily configuring many more custom integrations. - Would RexTheme consider adding means to implement custom marketplace templates in a more straightforward way?
- Any thoughts regarding out-of-the-box support for the two marketplaces mentioned? I could help test the implementation, or even contribute it myself with a little guidance regarding which classes I would need to create and which ones are best to start from (I’d love to get a lifetime subscription in such case though).
- This reply was modified 1 year, 7 months ago by Rimas.
I see. In that case I’ll just remove the plugin and replace it with a different one, which has support for multiple languages and WPML.
While I’m still waiting for the response, here’s another question: why do I only see one language in the list of languages during setup, when, as I mentioned, the website, and the WooCommerce shop supports multiple languages via WPML?
- This reply was modified 1 year, 7 months ago by Rimas.
To rephrase, I’m aware that there are target countries and languages that Google Merchant Center does not support, and Lithuania is among them. However, I’ve yet to see any indication that GMC supports same sets of countries and languages as both source (where goods are sold from) and target (where they are shipped to) though. Your plugin limits source countries and languages, and this sounds quite unreasonable.
Hi @doublezed2,
I understand that you didn’t really get the situation: I’m not asking the plugin to support more languages or countries then Google does. The problem is that two of the languages used by the store, as well as a multitude of countries, are supported by Google, but because the main/home language and country are not, the plugin refuses to allow configuring the ones that are supported.
I can’t find any indication on the webpage that you linked to that Google Merchant Center refuses to support businesses operating from Lithuania (it doesn’t) or using Lithuanian as primary language. The page talks about which countries and languages are supported by ads, but that’s not the same thing, is it?
Forum: Plugins
In reply to: [Headers Security Advanced & HSTS WP] Clash with Complianz cookie bannerThe right thing to do would be to make sure that all CSS stylesheets you use in your website indicate their MIME type correctly (
text/css).This was my mistake and I’m sorry for letting it slip. I’ve fixed it in Andrea’s private repo, and I hope he’ll release the fix soon.
Marking this thread as resolved, let’s continue over at https://ww.wp.xz.cn/support/topic/message-when-update-plugin/#post-16771887.
Forum: Plugins
In reply to: [Headers Security Advanced & HSTS WP] message when update pluginThis was my mistake and I’m sorry for letting it slip. I’ve fixed it in Andrea’s private repo, and I hope he’ll release the fix soon.
The headers are added using the
wp_headershook. I can only guess that that hook is not used by the login page. Are there any other hooks or filters we could use instead? Probably, but I don’t know (I’m not actually a fan of WordPress programming, so it’s no wonder I don’t know their API).If you check your wp-login.php on other websites using the SecurityHeaders service, you’ll likely notice the same symptom. At least that’s what happens when I check my wp-login.php: I’m getting a D rating here instead of A+ like I do with the homepage.
Let’s hope Andrea will take a deeper look. 🙂
- This reply was modified 3 years ago by Rimas.
Forum: Plugins
In reply to: [Headers Security Advanced & HSTS WP] NGINX SupportYes, this plugin does support Nginx. Not sure if it did 4 months ago, but now it definitely does.
Forum: Plugins
In reply to: [Headers Security Advanced & HSTS WP] Duplicate header info?This header duplication is likely the result of the plugin adding
Header setdirectives to.htaccess, but also adding these headers at response time.I don’t think it hurts, assuming both sets of headers are in sync (and they should be now), but I don’t think it adds much value either. I guess the only downside of not having these directives in
.htaccesswould be that they wouldn’t be sent with error responses and non-PHP responses such as file downloads. Which, at least to me, is acceptable.On the other hand,
.htaccessfile is Apache-specific, so, it has no effect whatsoever on Nginx and other web servers. Plus, even on Apache it may be ignored or even cause server configuration errors when it’s not ignored, but disallowed instructions are used.@unicorn03, would you consider dropping the
.htaccesssupport altogether? It would allow you remove a great deal of code from the plugin. Alternatively, it could be placed behind a settings checkbox or drop-down.One reason why I think this could happen is if you use Apache with a configuration which allows some rules in
.htaccess, but not other. This plugin adds severalHeader set(and used to addHeader always set) directives to.htaccess, and if Apache doesn’t allow this, you’ll be getting a configuration error.Forum: Plugins
In reply to: [Headers Security Advanced & HSTS WP] HSTS Header Present But Not WorkingCongrats! 🙂
Forum: Plugins
In reply to: [Headers Security Advanced & HSTS WP] Warning – HSTS preloadAs a PHP developer, I’d rather keep this as is, for two reasons:
- Even if that header has no effect over HTTP, it doesn’t hurt either
- It’s not always easy to detect whether your website is actually served via HTTP or HTTPS (for example, when it’s served via a reverse proxy or load balancer).
- Feature request: please make it possible to specify nested paths for custom attributes. For example, a custom attribute with name