nikostr0
Forum Replies Created
-
Thank you! I tried using only the last part of the link but no luck.
Perhaps I will disable the language switcher altogether, otherwise I’ll open a ticket like you suggested.
Thanks again!Hi Alex,
thank you. No, there are no separate posts for the languages; I just translate the strings in the frontend as usual.I have deactivated all plugins except Translatepress and activated the Twenty Twenty theme. Unfortunately the problem still persists.
Here are screenshots of my Translatepress settings: https://screensnap.de/share/ssenb2o2h2diL56QL68l/
Forum: Plugins
In reply to: [DHL Shipping Germany for WooCommerce] A4 label only takes up half a pageThank you! 🙂
This seems to be working okay. It generates a smaller label, but using the scaling option “Fit to paper” in the printing dialog, it gets stretched to the desired size.
https://drive.google.com/file/d/14R7uI_bQuWjiPLQKzOGvVoFmOGgDKUZx/view?usp=sharing
I will let the client know.
Forum: Plugins
In reply to: [DHL Shipping Germany for WooCommerce] A4 label only takes up half a pageThanks for your response!
But we don’t have “910-300-700” in the list – only A4 and some formats for Laser / Thermo Printer:https://drive.google.com/file/d/1MQcoG3rXz78ulwwnvCxhWC6_a0mtVZuU/view?usp=sharing 🤔
Plugin version is 2.2.7 and it was the same with 2.2.6
Forum: Plugins
In reply to: [Simple Membership] Protection not working with the new Divi Theme BuilderOk, so if you use the theme builder to display a custom header, footer, post titles, custom fields etc, access to this data won’t be restricted. Only the full post will be protected, which you will need to load via the “Fullwidth Post Content”-module.
So, you have a structure e.g. like
- Global Header (not protected)
- Body: Dynamic Title (not protected)
- Body: Fullwidth Post Content (protected)
- Body: Metadata, Custom fields etc. (not protected)
- Global Footer (not protected)
All the data will show apart from the fullwidth post content that will show the usual “no access rights” / “membership expired” / “not logged in” message.
Or if you have a project like me where there’s no post content at all and only the post meta and custom fields are relevant, your post won’t be protected at all.I worked around this by adding the “fullwidth post content”-module, which does not have any content but will still show the “no access rights”-message among the rest of the (not protected) content.
For this I added a short script that checks if this message -or rather the class belonging to it- is present (meaning that the user is not logged in, has an expired membership or a wrong membership level), and if it is, there’s a redirection to the login / signup page.
Make sure to put this at the very top of the body template (Fullwidth section -> fullwidth post content module and a fullwidth code module with the script underneath) so it gets loaded and executed before the rest of the content is loaded.<script> // check if user has access rights const errorcheck1 = document.getElementsByClassName("swpm-post-no-access-msg") if (errorcheck1.length > 0 ) { window.location.href = "/keine-berechtigung/" // link to a page notifying the user that their membership level is not sufficient } // check if membership has expired const errorcheck2 = document.getElementsByClassName("swpm-post-account-expired-msg") if (errorcheck2.length > 0 ) { window.location.href = "/premium-anmelden/" // link to your membership renewal page } // check if user is logged in const errorcheck3 = document.getElementsByClassName("swpm-post-not-logged-in-msg") if (errorcheck3.length > 0 ) { window.location.href = "/login/" // link to your login page } </script>- This reply was modified 6 years, 7 months ago by nikostr0.
Forum: Plugins
In reply to: [Simple Membership] Protection not working with the new Divi Theme BuilderThank you; it’s resolved. The problem is that for the theme builder, protection is only working with the Divi module “Fullwidth Post Content”, but not with dynamically generated content from Divi library items etc., which is not ideal but can be worked around.
Vielen Dank!
Ja, nach 3 Stunden ist klar; es ging um Bezahlungen, die unmittelbar nach der Bestellung erfolgen, aber dann liegt es wohl an IP/Browser/usw.