Gyakutsuki

@JcMappie, Ok Magento but for a little company go in this way it's crazy; The problem for this tool is the development and the maintenance. It's very expansive and need a specific knowledge if you want good performance. It's cool to present a framework like Laravel, or e-commerce platform like Magento, but there some solution like OpenCart, ClicShopping, LiteCart ... can make a best job without a big investment. Now the shopowner must evaluate what the need and what the evolution it wants. It doesn't want to do anything, Shopify or similar can be very good, to be more independent, it's another tool. The last thing is to take into consideration is the technology ecosystem and the maintenance for this ecosystem. Some tools can be good in a first approach, but in the time o be a disaster when you make a migration (example, prestashop) or an upgrade (odoo).

$error === false is use with a boolean.

The code you must integrate : just change the element in function (contact_us) $actionRecorder = new actionRecorder('ar_contact_us', (tep_session_is_registered('customer_id') ? $customer_id : null), $name); if (!$actionRecorder->canPerform()) { $error = true; $actionRecorder->record(false); $messageStack->add('contact', sprintf(ERROR_ACTION_RECORDER, (defined('MODULE_ACTION_RECORDER_CONTACT_US_EMAIL_MINUTES') ? (int)MODULE_ACTION_RECORDER_CONTACT_US_EMAIL_MINUTES : 15))); } if ($error == false) { .... $actionRecorder->record(); tep_redirect(tep_href_link('contact_us.php', 'action=success')); and

look contact form. Make the same thing inside account In contact form before the error === false, you must find the code and i the end before the redirection, you will find another code. Same thing in account before error === false include the same code and change contact by account before the redirection, same thing include the code. Don't forget to enable the module test, if succes, cool, no, you make a mistake.

Contact form is your base to work after you must update in consequence in your account.

Action recorder is in contact form and need also a module. You can use this ewample and update your code

The solution proposed by Burt is good. I have a customer in less 1 night, receive 80 000 emails. it's crazy. H had numeric captcha but not dynamic(like 5+four). In this case, a quickly test can be made. Now, the account form has action recorder, invisible captcha and a dynamic numeric captcha. Pb resolved The pb is the bot or the hacker change everytime the ip. In this case the recorder is not enough. Where is the pb ? I think the big problem come when you hide the state, in this case, it's more simple to fill the field. With the state enable, if you don't know a state, there is an error. If you decide to hide the states it's better to protect you.

They are 3 things to take in consideration. One for the customer account, it can be included inside the core and to be modular Second out of the customer account, in this case, it's better to have an add-on could be downloaded because it can be some consideration to take. use google analytics or not, Facebook ..... Every Thing is specific. for every shop. I make a contribution available on the forum tarteauxcitrons and recommended by the French CNIL. This script could be interesting. 3 Allow the administrator to satisfy a customer request.

@tgely I think important to take this rules. In case you approach does'nt work, It's important for all customer can accept or not the cookies You said cookies? With the GDPR, it is no longer possible to indicate on a site the following type of message "by visiting our site, we consider that you accept the use of cookies". You will now have to ask permission for each of the cookies used on your e-commerce site. On our side, we will also update our cookies policy on the SendCloud site and ask permission from all our users to store their cookies during visits to our site.

@tgely I suppose is not yet finished, it must have on the website a popup to accept or not the element ? Is it you idea at the end ?

@tgely : very interesting approach

Impressive development :)

If you want to finish the 2.4, and after to work with 2.4 now since very long month, I know very well. I think you must create a team Team for template HTML : got to boostrap2.4 Test team : go test and restest and try to break the functionalities Coder team : - After my experience, the most important in the first is to migrate general and classes directory in the first time inside OSC. The finalities is to have just one function and not 2 like the 2.3. The harmonisation allow to develop and adapt all element. HPDL begin to do that but currently is not yet finished. - The second thing is to respect the philosophy of the code, note like the last unofficial 2.3.5 . - The third thing is not to include new functionalities inside, just respect the current functionalities, Less is better than to go more; The spirit will be respected - The quater is to migrate the admin in app; App is great if you understand well what you can make with that and the relation between app across the hook About the biggest bug currently inside the 2.4 is the language, I open on github some element than I saw and the rewriting. I forgot lot of things but these elements are essentials if you want to make a beta prefinal and ready to work and easily to create new features in the futur. it' long work and lot of time, and I know, I can tell you ! Project management must make with a project leader take decision and orientation. Coherence ! +

@tgely Do you try something ? Do you want help ?

@tgely Let me more time to demonstrate something == I don't know ! :) Waiting

No Pb @tgely Lot of thing has been made on GDPR but not open to community at this moment. Also, than I read on the forum, the catalog is not taken. I am looking on github some script with GDPR and Citron seems to be good in the approach. Also, this script is made all inside. That's weakness in my opinion, doesn't let the people to create in function of their need but 80% use by users is inside for the free solution. I integrated lot of thing of this element maybe too for a test. If we think to integrated GDPR in the core, in this case, we must have something very modular and updated in function the different page - For all pages - For a specific page like products info Citron is a good approach to see the work. We have all elements with this script. About my approach : Yes Ii integrated a hooks because some ht module has a customization like google analytics. The ht citron is very long with all configuration, that's why I had thought to use hook for a specific configuration. After if you want to modify the hook and add option it's easy to customize. But it's manual. Now it's possible to create an admin page and manage all of that and write inside the db or to use a specific module. Other coders can let their opinion of the orientation must take for that.

@tgely I push the development on github: Note it works only on 2.4 . If someone want to update for 2.3, it will be cool https://github.com/Oscommerce24/ht_gdpr_tarte_au_citron

Ok, I will push github. I am finishing the script.

I found a solution inside the header tags. It's possible to call a hooks with the specific script options In this case the header_tags about google analytics is included inside the hooks and the configuration is managed by the Citron ! header tag. For Citron, I think use 90% of all user use inside their shop. if (MODULE_HEADER_TAGS_GDPR_TARTE_AU_CITRON_PLUGIN_GOOGLE_ANALYTICS_GA == 'True') { $google_analytics_ga = $OSCOM_Hooks->output('HeaderTags', 'GDPRGoogleAnalyticsGa'); // $google_analytics_ga = '<script type="text/javascript">tarteaucitron.user.gajsUa = \'' . MODULE_HEADER_TAGS_GDPR_TARTE_AU_CITRON_PLUGIN_GOOGLE_ANALYTICS_GA_ACCOUNT_ID .'\';tarteaucitron.user.gajsMore = function () { /* add here your optionnal _ga.push() */ };(tarteaucitron.job = tarteaucitron.job || []).push(\'gajs\');</script>'; } like you can see, the script does'nt take option (too specific), That's why inside a hooks it's possible to create differents function and after display information $this->getOption() $output = '<script type="text/javascript">tarteaucitron.user.gajsUa = \'' . MODULE_HEADER_TAGS_GDPR_TARTE_AU_CITRON_PLUGIN_GOOGLE_ANALYTICS_GA_ACCOUNT_ID .'\';tarteaucitron.user.gajsMore = function () { ' . $this->getOption() . ' };(tarteaucitron.job = tarteaucitron.job || []).push(\'gajs\');</script>'; Now it's possible to create the hooks in consequence. Advantage, The headertags code is not surchaged Inconvenient : All is not automatics but if the hook is not included inside, it's not a problem, you can create a hook and include in the directory later and it's automaticly use (if the element exists inside the header tag of course) It's possible to manage the social network more easily and display it on the good page for most of them (not again tested) Now all could be managed by one script, it's a good thing, I don't know, but in all the case it will be difficult to manage these elements with some script everywhere and to be correct with the GDPR.

Yes, you have right but most common used is implemented in tarteuacitron. Sent you a zip to test

Hello, I am working on a module GDPR. Please, let me know what the plug in you want inside this module. The most common used. https://opt-out.ferank.eu/en/install/

@Omar_one I don't know : no looking the approach and depends API also.

@tgely : I will make the app when it will be finished

@tgely Nice work, Why do you this develop this under apps ?

You can use moneris hosting, I don't think you will have this problem.