Jump to content

derailed

Members
  • Posts

    16
  • Joined

  • Last visited

1 Follower

derailed's Achievements

Newbie

Newbie (1/14)

2

Reputation

  1. Romaneste: eu am gasit o rezolvare , desi recunosc ca nu e cea mai potrivita ergonomic vorbind. Din pacate sunt doar programator de ocazie, mai mult designer si integrator. Eu am identificat legaturile, fisierele si modalitatea de editare, acum ar fi potrivit sa intervina un programator profi ca sa realizeze ce spui tu. English: I found the way to adress this issue, but I admitt it's not the most easy and ergonomic way to do it. I am an designer and integrater. I pointed the links, files and the way to modify the files, now it is time for a real programmer to step in and make what you requested: a way for the client to select it's status : company or individual. Let's hope someone in the prestashop staff will notice this request and adress it in feature versions.
  2. No, it's not a module and I don't think it's possible to make one ... you have to modify the BO files. But it would be nice if the Prestashop programmers would include a automatic way of adding aditional registration fields that could be managed by the BO.
  3. Yes Miha, it should work. I attached my AdminAddresses.php so you can compare code and troubleshoot your problem. Hope it helps AdminAddresses.php
  4. To add editable custom entries in the user cp you must edit two files : address.tpl and addresses.tpl in your theme's folder: 1. address.tpl: In the form declaration you must add the following two fieldsets ( modify names as needed): <input type="hidden" name="token" value="{$token}" /> {l s='CIF'} <input type="text" id="cif" name="cif" value="{if isset($smarty.post.cif)}{$smarty.post.cif}{else}{$address->cif|escape:'htmlall':'UTF-8'}{/if}" /> <input type="hidden" name="token" value="{$token}" /> {l s='Recom'} <input type="text" id="recom" name="recom" value="{if isset($smarty.post.recom)}{$smarty.post.recom}{else}{$address->recom|escape:'htmlall':'UTF-8'}{/if}" /> 2. addresses.tpl Just after : " {if $address.company}{$address.company}{/if} " on line 21 ( i guess ) you must add : {if $address.cif}{$address.cif}{/if} {if $address.recom}{$address.recom}{/if} ATTENTION: Follow all thread and make this modifications only after adding the custom columns to the mysql database.
  5. Hello ! Thank you for the error reports. The 1'st error I am aware of and actually can't seem to figure out what is the problem. It's not permissions related , and no modifications had been made to the mailalerts module, so I guess it must be database related. Maybe in my many shop upgrades something went wrong. The 2'nd error was caused by a missing address.php file, and now it's fixed. Thank you ! No the file name is correct , there is a address.php and one adresses.php file. Yes I have added the posibility to edit the CIF and Recom entries from within Front office and also Back office. I will post soon the steps to do it. I don't think it's posibble to make a module that will handle extra entries in the registration form since it requires modifyng core files. Maybe if someone would implement this feature in the official release. Marius
  6. Solved ! So to add for example a "Company' field in the customers list add this line in in AdminCustomers.php: ‘company’ => array(‘title’ => $this->l(‘Company’), ‘width’ => 80) in AdminCustomers.php To make the new column populate with the correct entries you need to add this to the $this->=_select query: (SELECT company FROM '._DB_PREFIX_.'address g WHERE g.id_customer = a.id_customer LIMIT 1 ) as company So now the final query looks like this : $this->_select = '(YEAR(NOW()) - YEAR(birthday)) as age, ( SELECT c.date_add FROM '._DB_PREFIX_.'guest g LEFT JOIN '._DB_PREFIX_.'connections c ON c.id_guest = g.id_guest WHERE g.id_customer = a.id_customer ORDER BY c.date_add DESC LIMIT 1 ) as connect,( SELECT company FROM '._DB_PREFIX_.'address g WHERE g.id_customer = a.id_customer LIMIT 1 ) as company '; And that's all. It's simple to adapt now to any entry in the adress table. Hope you get it to work with this dirrections, in not, PM me. Marius
  7. Hi ! Well it's nice to see that my little tutorial to add reg. info to database has helped someone. I am also working on solving your problem of adding a working field with the custom info in the customers table. UPDATE: Solved below :
  8. Hello ! After upgrading prestashop from 1.0 to 1.2 it seems my shop has lost the ability to send PDF invoices attachments in the clients e-mail. Is this by design or is there something wrong ? If it's by design , can it be configured to send pdf invoices? Thank you, Marius
  9. SOLVED ! I solved the problem by uninstalling and installing again the Quick Search Block Menu !
  10. Unfortunately it's not an easy task ... you must do it manually. It is a shame since it's such a important thing to have a customizable invoice, since different countries require different formats, and since there are already great open source projects like http://www.simpleinvoices.org/ that could be incorporated in some form in prestashop.
  11. SOLVED ! I solved the problem by uninstalling and installing again the Quick Search Block Menu !
  12. There is a solution posted here : http://www.prestashop.com/forums/viewthread/11135/P15/rapports_de_bugs/numero_de_facture it fixes the invoice number , but the date of the invoice is still not displayed. This is an actual confirmed bug and it can be tracked here : http://www.prestashop.com/bug_tracker/view/1306/
  13. Hi, I have a problem , maybe bug: In the invoice attached to the confirmation e-mail that comes to the client, there is a PDF invoice attached. All the pdf invoices that arrive attached have the number : NR. FACTURAIN000000 ( romanian ) The name of the invoice file is correct , and the invoice number for the invoice downloaded in the client's my account panel, or in the back office are correct. Only the invoice that comes in the email is wrong. Please can someone point me in the right dirrection? Thank you, Marius
×
×
  • Create New...

Important Information

Cookies ensure the smooth running of our services. Using these, you accept the use of cookies. Learn More