Jump to content

prestowicz

Members
  • Posts

    16
  • Joined

  • Last visited

  • Days Won

    1

prestowicz last won the day on June 21 2023

prestowicz had the most liked content!

Profile Information

  • First Name
    Robert
  • Last Name
    Darski

Recent Profile Visitors

255 profile views

prestowicz's Achievements

Newbie

Newbie (1/14)

9

Reputation

  1. 2020 - same here - increasing file upload size in BO seams to be the only way (and in php.ini) - this sucks because many modules exceed the standard 2MB file upload size - PS team work on that, installing vis FTP is vital 4us. cheers
  2. Hi, do you mean this theme ? https://waterthemes.com/neutral/14-home-appliances-prestashop-theme.html I have a theme module with the same mega menu functionality i guess (it's name is : WT Megamenu v1.1.0 But I don't have any eval string in the filenames or contet. Maybe you got hit by some other backdor or outdated module or FTP password manager leak.
  3. This one is easy. I also like to test functionality with diffrent modules and use this frequently. Run this SQL in your PHPMYADMIN or SQL CONSOLE : UPDATE `ps_customer` SET `is_guest` = '0' WHERE `ps_customer`.`id_customer` = <customer_id>; where <customer_id> is the number of the desired customer (you can get it from BO Clients table with ID column prefix)
  4. Worth to mention, if you seek a way to keep consistent with login state and its cookies values set (update or set override method for Cookie->mylogout() method and add unset() value for added cookie value, otherwise you can run out of sync with your code if it has a complicated logic behind later). class Cookie extends CookieCore { /** * Soft logout, delete everything links to the customer * but leave there affiliate's informations. * As of version 1.5 don't call this function, use Customer::mylogout() instead; */ public function mylogout() { unset($this->_content['id_compare']); unset($this->_content['id_customer']); unset($this->_content['id_guest']); unset($this->_content['is_guest']); unset($this->_content['id_connections']); unset($this->_content['customer_lastname']); unset($this->_content['customer_firstname']); unset($this->_content['passwd']); unset($this->_content['logged']); unset($this->_content['email']); unset($this->_content['id_cart']); unset($this->_content['id_address_invoice']); unset($this->_content['id_address_delivery']); unset($this->_content['firstTimeLogged']);//custom first time logg event variable watch $this->_modified = true; } }
  5. I don't know exactly what your code does look like, but in my case, I have an controller override where I need to obtain some translation labels from the global lang theme directory. I build and translate override function which behaves like the Translate.php getModuleTranslation() function. See my attached php Translate file. Usage: $txt = Translate::getControllerTranslation('product', 'full'); where 'product' is the translation view from the ProductController in PS BO translation page and 'full' is the desired translated label. Via this code you access the $_LANG gloabl variable (and not the $_MODULE like in previous examples)
  6. PS 1.6.4.1 on LITESPEED server - no email is send out from BO or front after order completition. Unknown error w linii 112 w pliku /home/ps/domains/psphp7/public_html/tools/pear/PEAR.php [8192] Methods with the same name as their class will not be constructors in a future version of PHP; PEAR has a deprecated constructor Unknown error w linii 829 w pliku /home/ps/domains/psphp7/public_html/tools/pear/PEAR.php [8192] Methods with the same name as their class will not be constructors in a future version of PHP; PEAR_Error has a deprecated constructor #EDIT constructor change: public function __construct resolved this error but still no @ are send out #EDIT 2 solved, some mail server policy prevented outgoing @ to be sent from dev env. when using prod. @ address #EDIT 3 While mailing advanced smtp setting when saving: Fatal error: Uncaught Error: Access to undeclared static property: Validate::$values in /home/ps/psphp7public_html/classes/controller/AdminController.php:1383 Stack trace: #0 /home/ps/psphp7/public_html/classes/controller/AdminController.php(897): AdminControllerCore->processUpdateOptions() #1 /home/ps/psphp7/public_html/classes/controller/Controller.php(178): AdminControllerCore->postProcess() #2 /home/ps/psphp7/public_html/classes/Dispatcher.php(367): ControllerCore->run() #3 /home/ps/psphp7/public_html/admin107prs/index.php(58): DispatcherCore->dispatch() #4 {main} thrown in /home/ps/psphp7/public_html/classes/controller/AdminController.php on line 1383
  7. Got a similiar error after switching PS 1.6.4.1 to PHP 7, no emails are send, after DEV_DEBUGING got some info: /public_html/tools/pear/PEAR.php [8192] Methods with the same name as their class will not be constructors in a future version of PHP; PEAR has a deprecated constructor will go deeper into that #EDIT change class name method to : public function __construct
  8. the best part, no module needed, inbuild presta functionality
  9. Try : {if Group::getCurrent()->id == 4} {* YOUR CODE *} {/if}
  10. gosh, so much overcomplicated.... why not: {Group::getCurrent()->id} will make the customer (user) default (most specific one) group available in template (tested on PS 1.6.1.1 from product.tpl)
  11. public function renderForm() { parent::__construct(); //parent::setMedia(); $this->addJS(_PS_MODULE_DIR_.'module/js/admin_product.js'); } I call parent::__construct(); and then inject the needed CSS or JS, if not working try with uncommented parent::setMedia(); method. Working fine with presta 1.6.1.1
  12. Guys, the following is needed to proper install: 1) Module in zip archive 2) Zip file structure: variableshipping.zip [ archive ] variableshipping [directory ] ...... [ content ] Had to shorten the direcotry depth because in default it was 2-level depth and change the name to module name: "variableshipping" and it's working. At presta version 1.6.1.1 and 1.6.1.0 no price edit possible, working to change that.
  13. Fought you were right with serialized data about speed but http://www.shozab.com/php-serialization-vs-json-encoding-for-an-array/ json is the absolute winner isn't it?
  14. Presta shop 1.6.1.1 Directory: /public_html/cache/cachefs/ and subdirecotories are writeable (permission: 777 for testing) Each page reload with cachefs (file system cache) does not cache the entry (backend CMS option Cache is enabled) I would like to work with presta Cache object for several reasons, future deployment will result in a memcache version. Does someone of you can confirm that cachefs is working? On the web I see others have also problem with cachefs: http://forge.prestashop.com/browse/PSCSX-7149
×
×
  • Create New...