Jump to content

machiavellino

Members
  • Posts

    9
  • Joined

  • Last visited

Profile Information

  • First Name
    G
  • Last Name
    M

machiavellino's Achievements

Newbie

Newbie (1/14)

2

Reputation

  1. I opened a ticket, i let the person who got the ticket assigned knnw that the problem was occuring to other people too, by pointing out another similar ticket. My ticked got closed as duplicate, but the other ticket is not being considered (it is opened in may, no response from staff, just from other people with the same problem). Anyone has an idea on where in php code is located the generation from templates? I cant' go live until i fix this problem!
  2. In PrestaShop Shop 1.7 after paying with paypal, in the page of the order confirmation i get the right email address in the phrase. "Your order has been confermed. An email has been sento to your address [email protected]." But the user gets no email. I found out that the smtp server is receiving email with the wrong recepient. In all the email body and headers, every occurrence of the two characters "id" are replaced with "pay-8j952046xj3882036librj7i", so the email address of the "to:" field "[email protected]" becomes "[email protected]" and is sent to this non existant mailbox. Example of substitution in the email body: What it should be: X-Rid: info@g Message-ID: <20171108143119.1147818576.swift@g> Date: Wed, 08 Nov 2017 15:31:19 +0100 Subject: [ Conferma ordine From: <INFO@g> Reply-To: info@g To: Gido mar <[email protected]> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_=_swift_v4_1510151479_85fbc0b7ea235df8b6ae1edcb642232f_=_" --_=_swift_v4_1510151479_85fbc0b7ea235df8b6ae1edcb642232f_=_ Content-Type: multipart/alternative; boundary="_=_swift_v4_1510151479_47796dac361c03798bdeee8a6184dc6a_=_" --_=_swift_v4_1510151479_47796dac361c03798bdeee8a6184dc6a_=_ Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable []=20 Hello Gido Mar .... - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - What is sent to the smtp server: X-Rid: info@g Message-ID: <20171108143119.1147818576.swift@g> Date: Wed, 08 Nov 2017 15:31:19 +0100 Subject: [ Conferma ordine From: <info@g> Reply-To: info@g To: GPAY-8J952046XJ3882036LIBRJ7Io mar <[email protected]> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_=_swift_v4_1510151479_85fbc0b7ea235df8b6ae1edcb642232f_=_" --_=_swift_v4_1510151479_85fbc0b7ea235df8b6ae1edcb642232f_=_ Content-Type: multipart/alternative; boundary="_=_swift_v4_1510151479_47796dac361c03798bdeee8a6184dc6a_=_" --_=_swift_v4_1510151479_47796dac361c03798bdeee8a6184dc6a_=_ Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable []=20 Hello GPAY-8J952046XJ3882036LIBRJ7Io Mar .... Does anyone knows the php file(s) that is responsible for generating the emails? It looks like something is replacing "id" with the payment id, instead of replacing something like "{id}" with the payment id (assuming that the pay-8j952046xj3882036librj7i string is the id returned by paypal). Thank you
  3. I had finally some time to check the code, and i found that the problems lies in the content of the variable "nextEncodedFacets" i opened a page where in the url i have the "q=Marca-APOLLO/Raggio-R16" referring to the feature visualized with the drop down list: the following values are referred to a feature with lower index (Altezza) (so it is higher in the widget layout), and selecting a value for this feature yelds no problem at all. 2 => Array (7) label => "Altezza" displayed => true type => "feature" properties => Array (1) id_feature => 1 filters => Array (7) 0 => Array (10) label => "45" type => "feature" active => null displayed => true properties => Array (0) magnitude => 3 value => 37 nextEncodedFacets => "Marca-APOLLO/Raggio-R16/Altezza-45" facetLabel => "Altezza" nextEncodedFacetsURL => "http://eni.fotovallescrivia.it/2-home..." The following values are referred to: a feature that has a higher index than the drop down list feature, and nextEncodedFacets => "Marca-APOLLO/Carico-84." is missing the "Raggio-R16". So, if i select a value for this or any other feature lower than the drop down list, the value "R16" is deselected from the filter! 9 => Array (7) label => "Carico" displayed => true type => "feature" properties => Array (1) id_feature => 13 filters => Array (17) 0 => Array (10) label => "84." type => "feature" active => null displayed => true properties => Array (0) magnitude => 2 value => 200 nextEncodedFacets => "Marca-APOLLO/Carico-84." facetLabel => "Carico" nextEncodedFacetsURL => "http://eni.fotovallescrivia.it/2-home..." Can someone give me a hint on where to look for the code that populate the "filters" array, which contains the "nextEncodedFacets" values? I've tryed themes/classic/modules/ps_facetedsearch and /modules/ps_facetedsearch but found nothing.. Any help would be appreciated, thanks.
  4. The problem persists in 1.7.1.0 beta. Introducing a dropdown or radio makes the layered search unusable. I'm posting a bug report. Meanwhile, do you know in which php files i should look (even if i prefered not to) to see if i can work this around? it looks like a problem one can solve "easily" once you got the right part of code in your hands.
  5. I'm currently using 1.7.0.5 and 1.7.0.4 on both linux and windows apache. I'll try the beta version to check if the problem is still there. But i hope it will be released an update of the layered search module for 1.7.0.5 too. Thank you for your reply, i'll let you know.
  6. Hello everybody, i found a quite annoying problem with dropdown and radio buttons in layered search. The symtpoms are then when in the front office you choose a value for a feature (or category, or manufacturer) that in the layered filter is positioned lower than a dropdown or a radio button, every chosen dropdown or radio button value that is positioned higher is then reset. This means that the layered search is unusable if you need a dropdown. Everytime you set a value below the one set in dropdown(s), every value chosen in the dropdown(s) is reset. This is because i noticed that when selecting a checkbox higher than the dropdown, the "search url" in the dropbox code is something like "http://casa.fotovallescrivia.it/12-auto?order=product.position.asc&q=Raggio-R16/ClasseEnergetica-E./Rumore-2/Altezza-45" where "Raggio-R16" is the feature-value of the dropdown value currently selected. in the same page, at the same moment, the "search url" of every other checkbox code lower than the dropdown, is missing the "Raggio-R16/" "http://casa.fotovallescrivia.it/12-auto?order=product.position.asc&q=ClasseEnergetica-E./Rumore-2/Larghezza-195" You can see that in the attachment: so, when i select or deselect a checkbox lower than the dropdown, the value selected in the dropdown is reset. so, it is impossible to use the dropdown. How is this possible? nobody uses dropdowns? This happens only with dropdowns or ratdio. Checkboxes are working fine. Where should i investigate to have this problem solved (i want al checkoxes, higher and lower than the dropdown, to keep the selected dropdown value when checked/unchecked)? This is happening even on a fresh install with the test database, if you just introduce one dropdown higher than a checkbox.
  7. Figured out the pattern which lead to the problem: it has everything to do with the order of filters. If i select a value in a filter that is "below" (in the left column of layered filtering), every filter that comes before is reset. I see that is the order filters name/values appear in the ?q= url parameter. If i change a value of a filter that is more to the right in the url, every set dropdown or radio filter on his left is reset. not checkboxes.. But i can't understand why...
  8. Hello everyone, i'm experiencing a problem with both prestashop 1.7.0.4 and 0.5 in both apache for windows and for linux. When using layered filters (even with the original database data), if i set up some (more than one) filters as dropdown or radio, when i select a filter value in one of the filters (both checkbox, radio or dropdown) SOMETIME a previously selected dropdown or radio filter is reset to no selected value. If i repeat the selection using a different sequence (for example setting dropdown values first, then checkbox values) the filters work. Checkbox filter are never reset to none. Just radio and dropbox ones after reload due to change in any of the selected filters values (but this is not happening consistently). I can't figure out what is happening. If i use just checkbox, everything is fine. Here is a development server 1.7.0.4 apache windows. The same happens to me in linux or 1.7.0.5 http://casa.fotovallescrivia.it/12-auto Anyone as any idea?
  9. HO anche io lo stesso problema. Non riesco a capire come editare *testo e html( il contenuto della home, o come creare nuove pagine statiche.. un aiuto sarebbe gradito.
×
×
  • Create New...