Jump to content
thirty bees forum

DRMasterChief

Members
  • Posts

    586
  • Joined

  • Last visited

  • Days Won

    12

Everything posted by DRMasterChief

  1. thank you, but there is no /mails/de (also no /mails/en) in the "my theme"-folder but also not in /themes/community-theme-default ?!?
  2. Thank you Slick, i already have replaced the theme contact-form with the original tb´s (it is a known problem that the contact form often does not work from themes, you have to re-upload or replace it then and it works, a lot of Prestashop versions got this problem). So at the moment i use the original tb´s contact-form with only small changes like buttons etc... but the problem with de language still appears.
  3. Yes i know, it is necessary to give some information to the customer also about the contact-from in the privacy policy. But... as i have written, it is "strongly recommended" to have a checkbox with a short note to the privacy policy (the same at the end of the checkout here in EU). This is to obviate against hasty bills from lawyers and protracted discussion with them regarding this. Maybe it is not that much work to include such thing in the contact-form?
  4. ah ok, to have a checkbox on the contact-form (e.g. http://front.thirtybees.com/contact-us ) with an link and hint for the privacy policy so customers have to mark it and confirm that they know where to read the privacy policy…
  5. https://thirtybees.com/blog/thirty-bees-and-gdpr/ will this include such a solution and/or do you think about it? thank you
  6. Hi again, regarding this thing with contact_form and your work on 1.0.4. with GDPR-module.... another question: it is strongly recommended to have a checkbox with an link and hint for the privacy policy so customers have to mark it and confirm that they know where to read the privacy policy.... (maybe someone read it of course). "Strongly recommended" means, that there is no actual judge from a court about this and to prevent from some bad guys it is much better to have such an text with checkbox on the contact form. Will the tb GDPR module for 1.0.4 include such a solution?
  7. Hello, last days i have seen the reCaptcha module for TB and i think i will install it (at the moment no spam, regarding TB shop is not in public yet). Regarding this, i expect the following: There is a problem with sending the contact-form.tpl : I have installed TB with German language, the English language was added later. So there is de and en to choose for customers. When i am with German language, the contact form does not work, there is an error called "Es gibt 1 Fehler Beim Senden der Nachricht ist ein Fehler aufgetreten" in a red field. In English language the contact form works fine and customer can send it. A green notification is shown. I have no solution for this. I am not with the standard theme, but this theme works with TB and there are no other problems evoked from this theme, so i think it is also in this case not a problem caused by the theme. I was not sure about the category, so if an admin think this is an technical problem, please move it. Anyone with an idea? In PS forum i have seen that there are -maybe- some php files to copy from the language to the other one (from de to en in my case, or vice versa?). thank you
  8. Hello, yes, solved means that i could delete the content in the database as described and after that, i could reach the BO again. Now there is no content in "customer > customer service" (blank fields) as it was before. I have no further details about the timeout (it was 504 Gateway timeout). I am on a professional hosting package but i am not sure if i have an access to the correct server logs! Important is that everything work and i dont have to manage all these server-things.... Any hint for me where to search for such logs?
  9. Great. Check if all languages work with the contact form (if you had several languages). At the moment, i have a problem with German translation: when i am with German language, the contact form does not work (error: Es gibt 1 Fehler Beim Senden der Nachricht ist ein Fehler aufgetreten). In English the contact from works like a charm. I have no solution for this :(
  10. Found the solution! In sql manager ( e.g. phpmyadmin ) , find for imap : SELECT * FROM ps_configuration WHERE NAME like '%imap%' OR pop SELECT * FROM ps_configuration WHERE NAME like '%pop%' and you can see the configuration value you need to delete.
  11. Hello, i have tried to fill my IMAP data in customer>customer service , but it seems that there is a problem with my data. Now i get a 504 timeout from nginx after a while, nothing appears and i cant reach the "customer>customer service" site again. All other BO sites are working, but not this one. There is no content in the database field "customermessagesync_imap" (i thought maybe i can clear this). Any help please :)
  12. Hi, not sure if this helps you, but if you are using not the original theme, you have to copy the default code of the contact-form.tpl and paste this to your theme's contact-form.tpl code. This helps in my case, i am not using the default TB theme.
  13. Hello, it´s the logo at the end of checkout, when you choose the payment method. But yes, thank you, i will replace this with an smaller logo and give the same name. one more question: Is there a perfect solution for responsive use, e.g. a smaller logo for tablet and smartphone users and how can the shop handle this?
  14. Hi, sorry but i have to give this in German: lies mal hier schnell die ersten Zeilen durch, das trifft immer noch zu: https://www.e-recht24.de/artikel/datenschutz/8451-hinweispflicht-fuer-cookies.html Es ist eben eine EU-Richtlinie die in DE aber nie umgesetzt wurde, da das bisherige BDSG das besser geregelt hat :) Ist doch auch mal schön statt daß wir in DE immer nur das andersherum kennen. Und wenn ich Kunden in anderen EU-Ländern habe kanns mir dennoch praktisch egal sein, da DE-Recht gilt. Die neue DSGV wird es etwas anders regeln, aber da genügt es dennoch wenn die Datenschutzerklärung entsprechend gestaltet ist (da muss es drin stehen was die Rechtsgrundlage ist). Ob ePrivacy umgesetzt wird ist ja noch offen....
  15. Hello, i try the PP module and got the problem that it uses the logo "defaulthorizontallarge.png" as standard. This is a very large logo with 544x170px and crashes my Theme (and i think the standard TB Theme too). I am not sure if the problem is in the module or in my Theme (i am not using the standard Theme). But how can i get a solution that the module will use different PP logos when the customer comes via Smartphone or Tablet? I can change this large logo to a smaller one from the PP logo site (you can download a lot of logos there), but how can i make the logo responsive to the various customers devices? Found in the paypal.php the call for this logo, can i change this there? Any ideas or solutions about this? thank you
  16. I agree to the information from Ahmed Abderraham in this discussion: https://thirtybees.com/blog/thirty-bees-and-gdpr/ There is no need to put an Cookie warning, not at the moment and not with the new GDPR. There was a special thing for Cookies for UK only, but hey.... not for the rest of EU.
  17. Ah ok, i dont know the details about that. Maybe you can do this with customer groups?
  18. Hi, there is a module from Prestacraft "custom popup notification", this should also work with TB. There are also a lot of other (free) modules for that, just search, maybe also in https://store.thirtybees.com
  19. Hello, honestly i appreciate your idea and opinion. But the law does not require an automatism for exporting the data like an shopsystem can provide this. But it requires a little bit more an easy way for customer to delete their data. So this was the idea of my contribution, and not what i want.... but yes, i want this, regarding it is required by the law ;) Hope you will understand.
  20. Much more interesting would be a "delete" button in customer account (really!!). I am interested in GDPR and was already on some workshops about this. The exportation of customers data is not that important for most of the normal onlineshops, but it could be interesting for customers when they change the telecommunication provider or something like that (this was the intention for this part of GDPR law). I think people will not use this to transfer login-data from a toy shop to their wine shop..... :)
  21. Thank you for the hint to this module, but it is not necessary by law to give the customer such an easy possibility. The law just means that customers have the right to be informed about the data you are saving from them. It could be necessary to give the customer an easy way to delete his data, this should be as easy as possible if you go straight by the law, but this could be also done by an message from the customer to the onlineshop with the simple text "please delete all my personal data" - should be an allowed way for small shops. The GDPR says that a lot of things of this law has to be seen comparative to the business (also e.g. the data transferability to an other competitor, for small business it is ok to give this data in CSV or XML file, maybe 2 times, there is no need to do this unlimited without fee). 30 EUR is not that much for such an module, so we can talk and talk and talk about or just use this module. I can understand the point of view from lesley. It could be hard to see the meaningfulness of some laws, but i think it is the same with US laws or any other countries :) And it is much more hard to understand when laws are made like rubber band, but this cames from the EU and THERE IS a rethinking for such laws. The GDPR also says, that the information has to be given in "clear and easy speech" to the customers, and also the law is written relatively clear and you can understand it when you read it twice. TB is on a good way, a lot of things are working better than in other shopsystems (but yes, some things maybe are not finished, we will see....). Unit price works with discounts and different packagings/sizes, AEUC seems to work for 98% and so on. I am on a point i could say it is possible to use TB for an legal secure shop in EU, when you make some changes manually.
  22. Hello lesley, i absolutely can understand your headaches with Germany, or better say EU.... it´s not the first thing which seems to be stupid (discussed here in the forum) - but hopefully we can use TB here in future if you have an eye on some things for EU, i think also EU is a big market for TB and worth it. In general, if anyone says "Germany" for such things, you can be sure that this is a regulation for whole EU. Thank you!
  23. Neue Lösung in Sicht ?? https://www.prestashop.com/forums/topic/662685-download-aeuc-europ%C3%A4ische-rechtssicherheit-verbessertes-modul-ohne-cachefehler/ Fehler in der foreach -Schleife behoben?? Vielleicht auch für mdekker interessant, da der Fehler in TB scheinbar noch immer vorhanden ist: $newhook->name = $hookname; $new_hook->title = $hook['name']; //$newhook->title = $hookname; $new_hook->title = $hook['name']; Achtung, ich muss sagen daß ich diese "Lösung" nicht versucht habe, da es damit teilweise auch noch Probleme zu geben scheint. Was da genau die Ursache für die erneuten Probleme ist kann ich nicht sagen, weiß ich nicht. Sollte jeder selbst lesen und ergründen und zuletzt in seiner eigenen Konfiguration testen (vorher auf jeden Fall Backups aller dieser Dateien machen um schnell wieder zurück zu können) ! ! ! !
  24. you´re so correct :) installation is done now, thank you for support, going to bed now
×
×
  • Create New...