Jump to content
thirty bees forum

Raymond

Members
  • Posts

    75
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by Raymond

  1. I finally found this other post where another user approached the problem from a different side, cookies after changes in the zones and nations, I thus deleted the cookies on my browser to try out, and worked so far. This is the thread from which I got the hint:
  2. Hello I updated the geolitecity2 file, switched geolocation back on from preferences and again as visitor/guest I get to see the prices excluded taxes on the frontend, if I log in as a client again I see the prices as they should accoding to the configuration. What should I check to be able to use geolocation and have the prices shown as visitor/guest accordingly to the settings in the configuration?
  3. Hello While building and testing the website i never noticed problems with tax included or excluded displayed prices, further proceding into setting more features of the shop after a while I noticed an odd error as prices kept to be displayed with taxes or without taxes only when I was logged in as a customer accordingly to the customer group it belongs to. Oddly when not logged in as customerm thus as visitor or guest, prices were always shown wihtout taxes, and also taxes did not appear in the cart. After checking all settings related to the way prices have to be shown and not getting the culprit I recalled that I activated the Maxmind IP geolocator service, I tried to deactivate it and everything went back to work as normal as should.... I now try to update the Maxmind geolocation file and will check if still causes the problem or not, will post the results later on, for the time being for whoever notices these kind of errors aboutthe way prices are displayed please check also the geolocation service and find out if is the culprit.
  4. Give visibility to TB and having themes are both important things, if not visible people do not come to know it, if visible but lacking of fundamental resources people do come to know it but may decide to drop it deeming it "hard to use". It is clear that both aspects are very important. Best thing would be to do "noise" to make it as visible as possible when at least some variants of the current default themes can be used to invite people to try a "customized basic version"? Of course would be even much better if a new theme or more new themes can be offered....
  5. Hello, I am using TB 14, upgraded from TB1.3 I needed to change supplier for a product, I did it form the back office and noticed that the new setting is not saved no matter what... So I created a new test product, also in this case the supplier is not saved no matter what. What should I check to fix this? Thank you
  6. I contacted a software company, I explained them I want to use thirty bees... They told me that they would have evaluated the case of developing stuff for TB and give me an answer. The result is that they searched TB on google trends, as the results on google trends are poor they said that at the moment they won't do it..... So, yes, it is important to make "noise" about thirty bees, the more information about thirty bees is read around in internet the more TB might become of interest for developers. Also it is important to write to developers and ask them to do stuff for TB, the more they get inquiries about TB the more they will be considering the chance to work on it.
  7. Raymond

    tiktok

    This is just a personal opinion about tik tok and other famous so called "social networks". As far as I know only few kind of products can be successfully advertised on these social networks, I would say mainly cosmetics and voluptuary products, fashion stuff and the like. Apart for these categories I do suggest to do not use it, can be a great loss of time, the ROI is minimal or none, the kind of public one can attract is very "funny" too.... Furthermore, one can easily ruin own reputation on these networks. Besides that, all of these famous network are known to be strongly biased, have whacky security mechanisms, plenty of bots and alts, prone to ban for no reason or truly arguable reasons, often driven by algorithms which do lots of strange things.... One particular notice about tik tok, it is said to be even dangerous for what is concerning security and privacy, search news articles about, there are quite some odd information about. In general, if you want to do e-commerce you do want to promote YOUR company, not make other companies more and more visible thanks to your content, avoid using services that ask you to work for free or even pay to mainly just promote THEIR company in the practice... think about this, does tik tok (or any other one alike) pay you to add content to THEIR website? Same thing for the many marketplaces, their commission is pretty high, their TOS is very often bashing YOU and favouring THEMSELVES, do you really want to risk bad reviews and other kind of troubles while you do pay all that money to promote and make THEIR website great and plenty of content? Think well about these aspects before onboarding in such ventures, do work for yourself, do not work for free for others or even worst do not pay to work for others. Just my 5 cents about this topic
  8. Hello This is an old topic, however I'd like to add this information, I have a large experience using Store Manager https://www.prestashopmanager.com/order/ I am using also with Thirty bees, and so far with TB 1.4 seems to work fine. Unfortunately the Emagicone company at the moment seem to not have interest to keep Store Manager compatible with Thirty Bees, but of course if they see that there are potential clients they might well change their ideas about. I can witness that Store Manager is really good and useful, worth the price and a true time saver. I suggest to whoever is looking for a complete exhaustive import/export and offline manager software for TB to give it a try and contact Emagicone clearing that you would buy the license if they keep the compatibility with future versions of TB Overall the software is easy to configure, easy to learn, easy to use, can do a lot of things in a fraction of the time that would be needed using the backoffice. This software is not just about importing/exporting/managing but also about migration, backup, diagnostics, optimization and keeping an offline "copy" of the TB shop(s).... Give it a try, download the trial version and see how it is really useful. Best regards
  9. Hi About the first issue, I noticed that just updating the core updater fix that and doing new checks displays not errors, I wondered tough why files which are identical to the original ones are detected as modified even though were never edited. About the second issue, as I wrote that behaviour occurs even when the cache is disabled, and even if disabled for instance clearing it solves the problem, hard to tell why tough.
  10. Hello On TB1.3 I wanted to check for updates, I got a warning about the following allegedly modified files: cache/cachefs/index.php config/defines.inc.php themes/community-theme-default/order-address-advanced.tpl upload/.htaccess I compared the files with those found in the thirtybees-v1.3.0.zip file downloaded form TB website, and they are all identical Why is this happening? ----------------------- Another thing I noticed In the modules page when is the case one get a warning message showing a list of modules for which a new version is updated. Clicking on a module name in the list the module is shown in the lower right panel and can be updated clicking the button on the right, clicking this button the system seems to update it and give back a success message, but the button on the right is still shown as "update" button and not "configure" as expected. Clicking it again the same happens, apparently the module is updated and the success message is given but will still appear as a module to be updated. Clicking on the other modules to be updated the same thing happens, apparently is updated, you get success message and then appears as if the update was not done, so to be updated again. Insisting in doing this with all the other modules it might happen that some of the previously updated modules finally do result to be effectively updated, some do not anyway... At that point I thought to clear the cache, I thus opened the performance page, and noticed that on this installation I did not even activate the cache, I cleared the cache anyway, returned to the modules page, updated the modules still in the list and finally I could update them one by one. On another installation of TB1.3 I noticed the same phenomenon, the only difference in that case was that I had the cache activated, for the rest I noticed more less the same behaviour. In another occasion in TB 1.3 it happened that after trying to update and getting the same rssults as said above I had other things to do and I got back on it after some time, somewhat a couple of hours later, well, after that time I refreshed the page and the list of modules to be updated changed.... some were at that point considered updated, others still not... however re-updating those left marked as not updated resulted in having them all updated at first try... This makes me wonder, I do not understand this odd behaviour, cache activated or not clearing the cache might solve the glitch, but also waiting some time might solve the glitch, sometimes works straight away, some other times not... What can cause this strange thing? Thank you
  11. These bots filling the cart are pretty common. I have no idea why they do that, however, I observed it many times. If you do not want bots to fill up the cart you must use an addon that do not allow non registered users to use the cart, doing so only users who signed in will be able to use the cart. However doing so also conversion is harder, many some potential new clients might not proceed if they cannot simulate a purchase before signing in... So in order to take a decision much depends on the traffic you have, the resources of the server, the kind of products and customers you deal with.. and so on.. you need to evaluate pros and cons accordingly to your specific case
  12. Thank you DataKick for the information, your explication is very synthetic and clear to understand for the final users
  13. Hello This workaround is ok for those not using a powerful server but at the same time creates lots of time losses to those who do not have that problem. I think that leaving the chance to use a save all button while advising with a note to first back up the language files might be a middle way solution for the case?
  14. Hello Yes, I still got no idea why I could not see the errors... , is a log of all errors available, or maybe there is some setting to use to have a more verbose output? This module is needed to comply with the GDPR law, should be built in the core. Personally, since ever, I could never understand why there are so many CMS, e-commerce platforms and in general websites that do not have this feature to ease the user decision to quit and close the account.
  15. Hello Wakabayashi Thank you I have the debug mode enabled on this test installation, but I did not see errors (???), it did look alike strange to me, now that you tried and saw the errors this fact does look even stranger! I am taking of the debug function one can enable from within the backoffice (which I verified do act on the same file defines.inc.php in the config folder where I was used to manually set it as true or false...) However, thanks to your analysis, verdict and hint I did a round of tests. The mail alerts module was installed... Off topic, I thought to check which email alerts were configured in it, then I enabled the "coverage" email too with 0(products) as a value and when I saved I got this warning: " Warning line 235 in the file modules/mailalerts/mailalerts.php [2] count(): Parameter must be an array or an object that implements Countable " This above is not related to the topic here, however I do report it in case is useful to check any other bug in TB, btw, I tried to change again the settings in the module and I could save without errors... so I have no idea of why the warning was shown... the products comments module from TB was not installed, so eventually this was the culprit in my case. I tried to install and activate it, thus tried to use the userdel module in the front shop, the module worked as expected... I then added the two IF you suggested to the userdel.php file, tried again to use it in the front shop user account and it works fine in all cases now, just as should be. Was not hard to find the lines where to add the IF conditions, however I post here below how the code is modified now in my userdel.php file, from the line 356: // delete customer from mailalert module if (Module::isInstalled('mailalerts')) { $queries[] = "DELETE FROM `"._DB_PREFIX_."mailalert_customer_oos` WHERE id_customer = ".(int)$customer->id; } // delete customer from productcomment module if (Module::isInstalled('productcomments')) { $queries[] = "DELETE FROM `"._DB_PREFIX_."product_comment` WHERE id_customer = ".(int)$customer->id; // clean productcomment module $queries[] = "DELETE FROM `"._DB_PREFIX_."product_comment_grade` WHERE `id_product_comment` NOT IN (SELECT `id_product_comment` FROM `"._DB_PREFIX_."product_comment`)"; $queries[] = "DELETE FROM `"._DB_PREFIX_."product_comment_report` WHERE `id_product_comment` NOT IN (SELECT `id_product_comment` FROM `"._DB_PREFIX_."product_comment`)"; $queries[] = "DELETE FROM `"._DB_PREFIX_."product_comment_usefulness` WHERE `id_product_comment` NOT IN (SELECT `id_product_comment` FROM `"._DB_PREFIX_."product_comment`)"; } Thank you 🙂
  16. Hello Surely not all merchants want the same, but that's how it goes with every feature, module or else..., one thing is sure, to comply with GDPR all the data must be deleted when the user request it. The userdel module actually offer just 3 options in the admin panel there is a slider button to set the test mode or live mode, that to simulate and check if there are problems in general a second slider button allows to set the module to process or not process orders the third slider button if the second button is set to process orders allows to set the module to either keep the orders in the database in an anonymized form or delete the data That's all, actually this module does not offer other options On the front side the user in the account page has a button to see a resume of all the data (that is handled by the module, it could be enhanced to retrieve also other sensible data, e.g. newsletter subscription or else). In that page there is another button with which the user can delete the data and the whole account, if clicked the data will be erased and the orders will be either erased or anonymized accordingly to what the admin settled in the back office There are no other functions or options, at the moment, but I hope that this module could be developed to cover more aspects and possibilities. The module is very simple, seems that the most is done in one file named userdel.php which counts about just 421 lines, even not being a coder I can see more less what does It was working on previous versions of TB, since TB1.3 does not, as I wrote does not throw errors, pretty simply do not delete the account any more. I attached it, I guess is not hard to fix it. I also guess that could be used to enhance the TB GDPR compliance module (which by the way to be completed should also do more things), or something similar could be included in the core of TB. As I wrote in more posts according to me an e-commerce platform today should natively include these functionalities. Thank you userdel-module.zip
  17. Hello I agree with both, deleting might cause problems, but must be possible to delete things if done right, furthermore, definitely (being able to and) keeping the DB lean does not sound at all a bad idea, on the contrary I guess it is a good practice. I checked again the "free userdel module by Metacreo", it was given out for free on prestashop forum, then disappeared, the files inside are all marked with a GPL3 license, so Think there is no problem to share it here. IS it OK if I upload it here? Will anyone of you experts fix it or at least help me to fix it (I am no coder btw, but I can follow instructions) and share it back so everyone can use it? Maybe could also become a thirty bees free module once is fixed for good... Thank you Best regards
  18. Hello I noticed that switching theme a warning is given about non-theme related hooks being ignored. What is meant exactly by "non-theme related"? I have seen in the list that some of the modules are from the theme, why then are considered "non-theme related"? What does imply to have all those hooks not registered? At the end of the list there is a more serious warning about modules from the theme for which hooks where not defined in the theme's xml file, I will contact the developer as suggest, however, what kind of inconsistencies will be caused by this? The warning output is below Thank you Some warnings were encountered during theme installation. Following non-theme related hooks were ignored Theme instructs thirty bees core to register hooks that are not theme related. These requests were ignored Hook actionCartListOverride from module blockcart_mod Hook actionAdminLanguagesControllerStatusBefore from module blockcategories Hook actionAdminMetaControllerUpdate_optionsBefore from module blockcategories Hook actionCategoryAdd from module blockcategories Hook actionCategoryDelete from module blockcategories Hook actionCategoryUpdate from module blockcategories Hook displayBackOfficeCategory from module blockcategories Hook actionAttributeDelete from module blocklayered Hook actionAttributeGroupDelete from module blocklayered Hook actionAttributeGroupSave from module blocklayered Hook actionAttributePostProcess from module blocklayered Hook actionAttributeSave from module blocklayered Hook actionCategoryAdd from module blocklayered Hook actionCategoryDelete from module blocklayered Hook actionCategoryUpdate from module blocklayered Hook actionFeatureDelete from module blocklayered Hook actionFeatureSave from module blocklayered Hook actionFeatureValueDelete from module blocklayered Hook actionFeatureValueSave from module blocklayered Hook actionProductListOverride from module blocklayered Hook actionProductSave from module blocklayered Hook actionObjectCategoryDeleteAfter from module stbanner Hook actionObjectManufacturerDeleteAfter from module stbanner Hook actionShopDataDuplication from module stbanner Hook actionProductAdd from module stbestsellers Hook actionProductDelete from module stbestsellers Hook actionProductUpdate from module stbestsellers Hook GSitemapAppendUrls from module stblog Hook actionShopDataDuplication from module stblog Hook displayAdminHomeQuickLinks from module stblog Hook displayBackOfficeHeader from module stblog Hook moduleRoutes from module stblog Hook GSitemapAppendUrls from module stblogarchives Hook moduleRoutes from module stblogarchives Hook moduleRoutes from module stblogsearch Hook actionObjectManufacturerDeleteAfter from module stbrandsslider Hook displayAdminProductPriceFormFooter from module stcountdown Hook actionShopDataDuplication from module steasycontent Hook actionCategoryDelete from module steasytabs Hook actionProductAdd from module steasytabs Hook actionProductDelete from module steasytabs Hook actionProductUpdate from module steasytabs Hook displayAdminProductsExtra from module steasytabs Hook actionCategoryAdd from module stfeaturedcategories Hook actionCategoryDelete from module stfeaturedcategories Hook actionCategoryUpdate from module stfeaturedcategories Hook actionProductAdd from module stfeaturedslider Hook actionProductDelete from module stfeaturedslider Hook actionProductUpdate from module stfeaturedslider Hook actionProductAdd from module sthomenew Hook actionProductDelete from module sthomenew Hook actionProductUpdate from module sthomenew Hook displayBackOfficeHeader from module sthoverimage Hook actionObjectCategoryDeleteAfter from module stiosslider Hook actionShopDataDuplication from module stiosslider Hook actionCategoryAdd from module stmegamenu Hook actionCategoryDelete from module stmegamenu Hook actionCategoryUpdate from module stmegamenu Hook actionObjectCategoryDeleteAfter from module stmegamenu Hook actionObjectCategoryUpdateAfter from module stmegamenu Hook actionObjectCmsDeleteAfter from module stmegamenu Hook actionObjectCmsUpdateAfter from module stmegamenu Hook actionObjectManufacturerDeleteAfter from module stmegamenu Hook actionObjectProductUpdateAfter from module stmegamenu Hook actionObjectSupplierDeleteAfter from module stmegamenu Hook actionProductAdd from module stmegamenu Hook actionProductDelete from module stmegamenu Hook actionProductUpdate from module stmegamenu Hook actionShopDataDuplication from module stmegamenu Hook hookActionObjectProductDeleteAfter from module stmegamenu Hook actionObjectCategoryDeleteAfter from module stmultilink Hook actionObjectCategoryUpdateAfter from module stmultilink Hook actionObjectCmsDeleteAfter from module stmultilink Hook actionObjectCmsUpdateAfter from module stmultilink Hook actionObjectManufacturerDeleteAfter from module stmultilink Hook actionObjectManufacturerUpdateAfter from module stmultilink Hook actionObjectSupplierDeleteAfter from module stmultilink Hook actionObjectSupplierUpdateAfter from module stmultilink Hook actionShopDataDuplication from module stmultilink Hook actionCustomerAccountAdd from module stnewsletter Hook actionDeleteGDPRCustomer from module stnewsletter Hook actionExportGDPRData from module stnewsletter Hook registerGDPRConsent from module stnewsletter Hook actionObjectCategoryDeleteAfter from module stowlcarousel Hook actionObjectManufacturerDeleteAfter from module stowlcarousel Hook actionShopDataDuplication from module stowlcarousel Hook actionObjectCategoryDeleteAfter from module stpagebanner Hook actionObjectCmsDeleteAfter from module stpagebanner Hook actionObjectManufacturerDeleteAfter from module stpagebanner Hook actionObjectSupplierDeleteAfter from module stpagebanner Hook actionShopDataDuplication from module stpagebanner Hook actionShopDataDuplication from module stparallax Hook actionCategoryDelete from module stproductcategoriesslider Hook actionObjectCategoryDeleteAfter from module stproductcategoriesslider Hook actionProductAdd from module stproductcategoriesslider Hook actionProductDelete from module stproductcategoriesslider Hook actionProductUpdate from module stproductcategoriesslider Hook actionProductDelete from module strelatedproducts Hook actionProductUpdate from module strelatedproducts Hook displayAdminProductsExtra from module strelatedproducts Hook actionProductAdd from module stspecialslider Hook actionProductDelete from module stspecialslider Hook actionProductUpdate from module stspecialslider Hook displayAdminProductPriceFormFooter from module stspecialslider Hook actionShopDataDuplication from module stthemeeditor No hooks defined for following modules Theme installed or enabled following modules but didn't provide hook list for them. Theme should always provide hook list in order to achieve consistent results. If no hooks are specified in config.xml file, module hook list will remain unchanged. If this is wanted behaviour, theme developer should make it explicit by adding manageHooks="false" into module entry No hooks are defined for module stfblikebox in theme config.xml file No hooks are defined for module stblogcomments in theme config.xml file No hooks are defined for module stblogrelatedarticles in theme config.xml file No hooks are defined for module beesblogpopularposts in theme config.xml file Please contact theme developer and request correction of theme config.xml file
  19. Hello Yes I double checked, does not work, This is the manual of the module, all what in the manual is said that should be shown in the configuration panel of the module is not showing up, only the other panel reachable via the tab menu is showing up probably correctly, ut I ma not sure that works well, I cannot test the rest and I have no idea where to get the error log, nothing is show despite the debug mode is active. I will ask them, but i guess they will simply answer that is not for TB, that I bought it years ago and so on... who knows... maybe not... The question that rose from that is: if existing, which logs one can check in TB to find problems that do not throw an error while debug mode is on? However It is a bit of a long frustrating story overall... I bought that module in 2017, did work fine, then I stopped using it when upgraded to PS 1.6as the fields I needed could be covered recycling the SIRET, APE and DNI fields, this was even an advantage since GDPR started because all the GDPR modules surely do collect all data from those fields, while it is not sure that can collect data form new fields one add by hand or with modules (and of course one tends to not choose the complicate way, what works out of the box generally is better, does not seem a good idea to fiddle everywhere every time isn't it?). When I switched to TB I could use the same arrangement. Until TB 1.2 all went fine, with some workaround I could cover all basic aspects of registration, GDPR, including the possibility for the clients to delete their own account without having to ask for, having to delete the data upon request is just extra work for the merchant (the result is exactly the same, if the client want to delete data one has to delete it , that's it) Now with TB 1.3 I can't understand why the SIRET, APE DNI and also the other fields that can be added in the address format in the country do not show up in the registration form... Are those SIRET DNI APE OTHER fields definitely disabled? Is there a way to use it still? So I thought to get back to that custom registration fields module and see if I could put it in use again but seems that I am out of luck at this point Needless to say that just as it happened with many other modules, also expensive ones, I did not like this custom registration fields ting very much, it had its own issues too at the time, but at least worked for a while... and this point is quite important to be noted to better understand what is the final feeling I had using PS and that I do not want to get again... The reason for which I threw PS under the bus is that I constantly had to fiddle with the very basic things to no avail, it had been somehow a continuos loss of time for relatively "simple" basic things that should be as solid as the foundations of a system... The real trouble is that the world changed, while TB, PS and practically also all the others did not not change as much, today IMHO an e-commerce platform must have built in as basic core all these features required by GDPR and similar laws around the world. It is not just a matter of paying some money and time to get these features, the major problem is about reliability and security, it is all about to be reasonably sure that at least all these feature required by law in a growing amount of countries will work fine in the time also after updates and upgrades of the core. To get a clearer vision of what is happening I found this article: https://www.endpointprotector.com/blog/data-protection-legislation-around-the-world/ On the other side how many e-commerce platform do come out of the box with the features required built in and secured to be maintained in the time along with the ongoing core development? Maybe 0, nul , zero... Let's suppose that all these laws never existed or that will be ceased, so, let's go beyond the fact that these laws do exist, what's wrong in having a system that can be settled in such a way to build a transparent fair relation between services/goods' suppliers and the customers? Having easy way to clear pretty well forehand what the agreements are, get the clear consent of the users, let the users review, modify, retrieve and delete their own data/consents and/or delete their own account does not sound strange at all to me... this at least, I do not want to comment all the rest about these rules, but that part is quite understandable and shareable I think... just my 5 cents on this topic... Thank you for the help
  20. Hello I did what you said on the registration fields module, it could be installed, but entering it to configure it do shows only a line to add a registration field and a save button, and nothing else as it should. Trying to save the new registration field output that the field was saved and shows nothing else again but the same line to add a new registration field, seems that cannot work on TB.1.3 as it is done now. TB in this case does not output debug information tough, what should I do to get information from the system when does not throw error reports with debug mode on? Thank you
  21. I recalled that the GDPR module had the same problem since start with TB, and I already got help here back then, at that time you suggested to do the following found in this post, I did the same, seems that works again: I now try to install the module for the registration fields, thank you.
  22. Hi Data Bummer, yes, that is a bad new. However until the version 2.1.18 worked. I reverted to the last functional version I have... Too bad 😞 Which module for the GDPR would you suggest that is surely compatible with TB and that hopefully will keep being so? Thank you
  23. Thank you Data I will do it By the way, I uninstalled that module and did something else in the meanwhile, i updated another module, for GDPR... apparently worked, but then browsing in the configuration pages of the module I got this new error, which made the website throw the same error whatever menu item I click now Thank you ThirtyBeesException Cannot make static method ObjectModelCore::createDatabase() non static in class CustomObjectModel in file modules/gdprpro/src/CustomObjectModel.php at line 201 Source file: modules/gdprpro/src/CustomObjectModel.php 182: } 183: $sql .= $field_name . ' ' . $field['db_type']; 184: if (isset($field['required']) && $field['required']) { 185: $sql .= ' NOT NULL'; 186: } 187: if (isset($field['default'])) { 188: $sql .= ' DEFAULT "' . pSQL($field['default']) . '"'; 189: } 190: $sql .= ','; 191: } 192: $sql = trim($sql, ','); 193: $sql .= ')'; 194: Db::getInstance()->execute($sql); 195: //create multilang tables 196: if ($multilang) { 197: $sql = 'CREATE TABLE IF NOT EXISTS ' . _DB_PREFIX_ . $muchTableMuchProtected . '_lang ('; 198: $sql .= pSQL($definition['primary']) . ' INTEGER UNSIGNED NOT NULL,'; 199: $sql .= 'id_lang INTEGER UNSIGNED NOT NULL,'; 200: if ($definition['multilang_shop']) { 201: $sql .= 'id_shop INTEGER UNSIGNED NOT NULL,'; 202: } 203: foreach ($definition['fields'] as $field_name => $field) { 204: $field = $this->sanitizeColumnDefinition($field); 205: if ($field_name === $definition['primary']) { 206: continue; 207: } 208: if (!$field['lang']) { 209: continue; 210: } 211: $sql .= pSQL($field_name) . ' ' . pSQL($field['db_type']); Stack trace 1. modules/gdprpro/src/CustomObjectModel.php source Fatal error() 1:<?php 2:/** 3: * PrestaChamps 4: * 5: * NOTICE OF LICENSE 6: * 7: * This source file is subject to the Commercial License 8: * you can't distribute, modify or sell this code 9: * 10: * DISCLAIMER 11: * 12: * Do not edit or add to this file 13: * If you need help please contact leo@prestachamps.com 14: * 15: * @author PrestaChamps <leo@prestachamps.com> 16: * @copyright PrestaChamps 17: * @license commercial 18: */ 19: 20:/** 21: * Class CustomObjectModel 22: */ 23:abstract class CustomObjectModel extends ObjectModel 24:{ 25: /** 26: * Return informations of the columns that exists in the 27: * table relative to the ObjectModel. If the Model has multilang enabled, 28: * this method also returns information about the multilang table. 29: */ 30: public function getDatabaseColumns()
  24. Hello I tried to install a module to add new fields to the registration form, I got an internal server error, switched on debug and got this below... What should I do to solve it? Thank you ThirtyBeesException Cannot use string offset as an array in file modules/registrationfields/registrationfields.php at line 302 Source file: modules/registrationfields/registrationfields.php 283: $helper->allow_employee_form_lang = Configuration::get('PS_BO_ALLOW_EMPLOYEE_FORM_LANG') ? Configuration::get('PS_BO_ALLOW_EMPLOYEE_FORM_LANG') : 0; 284: $this->fields_form = array(); 285: 286: $helper->identifier = $this->identifier; 287: $helper->submit_action = 'submitConfiguration'; 288: $helper->currentIndex = $this->context->link->getAdminLink('AdminModules', false).'&configure='.$this->name.'&tab_module='.$this->tab.'&module_name='.$this->name; 289: $helper->token = Tools::getAdminTokenLite('AdminModules'); 290: $helper->tpl_vars = array( 291: 'fields_value' => $this->getConfigFieldsValues(), 292: 'languages' => $this->context->controller->getLanguages(), 293: 'id_language' => $this->context->language->id 294: ); 295: return $helper->generateForm(array($fields_form)); 296: } 297: 298: public function getConfigFieldsValues() 299: { 300: $return = ''; 301: foreach (Language::getLanguages(false) as $lang) { 302: $return['REGISTRATION_FIELDS_HEADING'][(int)$lang['id_lang']] = Tools::getValue('REGISTRATION_FIELDS_HEADING_'.(int)$lang['id_lang'], Configuration::get('REGISTRATION_FIELDS_HEADING', (int)$lang['id_lang'])); 303: } 304: return $return; 305: } 306: 307: public function hookActionCustomerAccountAdd($params) 308: { 309: $id_customer = (int)$this->context->cookie->id_customer; 310: $objModel = new Fields(); 311: $objModel->saveFieldValues(Tools::getValue('fields'), $id_customer); 312: } Stack trace 1. modules/registrationfields/registrationfields.php:291 source RegistrationFields->getConfigFieldsValues() 272: 'submit' => array( 273: 'title' => $this->l('Save'), 274: ) 275: ), 276: ); 277: 278: $helper = new HelperForm(); 279: $helper->show_toolbar = false; 280: $helper->table = $this->table; 281: $lang = new Language((int)Configuration::get('PS_LANG_DEFAULT')); 282: $helper->default_form_language = $lang->id; 283: $helper->allow_employee_form_lang = Configuration::get('PS_BO_ALLOW_EMPLOYEE_FORM_LANG') ? Configuration::get('PS_BO_ALLOW_EMPLOYEE_FORM_LANG') : 0; 284: $this->fields_form = array(); 285: 286: $helper->identifier = $this->identifier; 287: $helper->submit_action = 'submitConfiguration'; 288: $helper->currentIndex = $this->context->link->getAdminLink('AdminModules', false).'&configure='.$this->name.'&tab_module='.$this->tab.'&module_name='.$this->name; 289: $helper->token = Tools::getAdminTokenLite('AdminModules'); 290: $helper->tpl_vars = array( 291: 'fields_value' => $this->getConfigFieldsValues(), 292: 'languages' => $this->context->controller->getLanguages(), 293: 'id_language' => $this->context->language->id 294: ); 295: return $helper->generateForm(array($fields_form)); 296: } 297: 298: public function getConfigFieldsValues() 299: { 300: $return = ''; 301: foreach (Language::getLanguages(false) as $lang) { 2. modules/registrationfields/registrationfields.php:252 source RegistrationFields->renderForm() 233: Db::getInstance()->Execute('DROP TABLE IF EXISTS '._DB_PREFIX_.'fmm_registration_fields_shop'); 234: 235: return true; 236: } 237: 238: public function getContent() 239: { 240: $output = ''; 241: if (Tools::isSubmit('submitConfiguration')) { 242: $message_trads = array(); 243: foreach ($_POST as $key => $value) { 244: if (preg_match('/REGISTRATION_FIELDS_HEADING_/i', $key)) { 245: $id_lang = preg_split('/REGISTRATION_FIELDS_HEADING_/i', $key); 246: $message_trads[(int)$id_lang[1]] = $value; 247: } 248: } 249: Configuration::updateValue('REGISTRATION_FIELDS_HEADING', $message_trads, true); 250: $output .= $this->displayConfirmation($this->l('Configuration updated')); 251: } 252: return $output.$this->renderForm(); 253: } 254: 255: public function renderForm() 256: { 257: $fields_form = array( 258: 'form' => array( 259: 'legend' => array( 260: 'title' => $this->l('Configuration'), 261: 'icon' => 'icon-cogs' 262: ),
  25. Hello I used the " Module Delete User own Account v1.0 - by Metacreo " with success on Tb1, works fine, it allows to see the data, delete the data only or delete data and the entire user account, exactly what is needed to fully comply with part of the GDPR rules, best of all does not require the admin to intervene, which is a great thing (at least for my case and point of view, and btw, on the gdpr directive it is specified that the user should be able to operate without admin help). Now I am trying to use it on TB 1.3 and noticed that do not work any more. The module behaviour on TB 1.3 is the following: apparently does work, does not throw errors, the procedures are carried out, but data and account are NOT deleted, so in fact the user even after deleting the entire account keeps logged in, can see own account and data and even logging out then can login again and see all his data intact, repeating the operation does output same result. I tried it also on a fresh TB 1.3 installation with no other modules or themes installed but the original ones only. what did change in Tb1.3 that prevents the old method to delete data and account to work? I have no idea of where I should look at By the way, apart fixing this one that to my knowledge is the only one being simple and perfectly doing those 3 simple things right and without any hassle, does anyone know a module that can cover all the GDPR requirements that is known to work just fine with TB1.3? BTW, I agree with Slick 303, such a function should be built in and ready out of the box, so there would be no need to fiddle with modules and stuff to have this simple functionality, furthermore according to me all of the cookies and GDPR directives should be covered with built in tools, this is not only a way to meet those requirements, but also a way to allow dealers to setup more transparent and user friendly e-commerce websites in general, also in countries where all these rules are not mandatory (btw, there are over 20 major countries in EU, it comprises a population of hundreds of millions, it is not a marginal little market) Thank you for the help.
×
×
  • Create New...