Jump to content

Welcome, Guest!

By registering with us, you'll be able to discuss, share and private message with other members of our community.


  • Content Count

  • Joined

  • Last visited

Community Reputation

42 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I got a customer who wanted to order via paylater/pay via invoice but canceled the checkout. In a nutshell he did not order. Then he called us and wanted me to order. No problem I say but a problem occurs: I can not Add new address for the customer no matter I do. Under customers he appeard two times. I deleted the older entry after not being able to save adress data from back office since I hoped that might help. But it did not. I use latest 'bleeding edge' and can need help since I need to make this order for the customer.
  2. I have a small change to my /js/admin.js that adds the function to mass download invoices. This is incredible helpful to me since I a have a tool running in the background of my OS that monitors my download folder for 'invoice.php'/'invoice.pdf' and send it directly to my printer and moves them then to another folder where my archive tool grabs them... If you change the file with the given lines of code you will get an additionl button in back office order at the bottom where the 'Action' button sits. $('body.adminorders .bulk-actions ul').append('<li><a href="#" id="downloadBulkSingle"><i class="icon-download"></i> Bulk InVOICE download</a></li>'); $('a#downloadBulkSingle').click(function(e){ e.preventDefault(); $('[name="orderBox[]"]:checked').each((i,e)=> $(e).parents('tr').find('a[href*="generateInvoicePDF"]').each((a,c) => c.click())); }); I inserted it into line 911.
  3. Hello I use the Warehouse theme by Iquit and I want to make use of the JASON/LD module. I set up last week GoogleTagManager and thought that it might be also a good idea to get the named module with proper markup running. So, I am looking for some detailed documentation and setup instructions of the module. What I read is that I have to make sure that my template does not use any markup code. Well, Well... First I thought, easy, just look into product.tpl and category.tpl and delete anything that looks like markup. After recognizing the markup code tag I could also make a text search through the whole template folder... Then I thought, mh, may be some modules like cross-selling could also have some markup code implemented. You dig it, I have no real clue in this case what to do. So, perhaps some one could hint me the way?
  4. Pedalman

    Looking for a Mega Menu

    There are at least two posts in the forum (technical problems is guess) that might be related to the 500er error. I use Warehouse too and ran into problems with saving 'content creator' module changes as pasting css into the theme editor form with TB1.0.8. I cloned my shop did a successfull test and repeated the same on my live shop yesterday and these two issues are gone. I did install the core updater module and updated to 'bleeding edge' version that reflects the latest GIT commits on the developing road so to speak. This I did since I believe Petr commited on Jan. 18th a fix relating to this issues. But I am just a merchant and the good ones here should give you the right hint. good luck PS: before trying what I did try to make changes in 'your' content creator module and to save them. Might be you get this 500er error and you know 😉
  5. Hi Markus, you answered my question perfectly. Id did not know exactly what 'bleeding edge' reflects concerning the git commits. I did now the 1.0.x update on my live shop (yes, I am a bit of the risky type but that is also the reason why I am here since more than a year) and the problem is mostly gone. Saying mostly since before 1.0.8 I guess I could paste my css code nicely formatted into the corresponging form of my theme editor and it was saved like that. Now, all pre-formatting /beautifying is gone after saving and css code is 'pressed' into one long line in the form. But good news is that the escapes have gone and all works. Thank you very much
  6. I think that the damn cool core updater module has a problem with a local install of Thirtybees under XAMPP Windows. Downloads calculated, 7632 files to download. (0.1 s) ERROR: Failed to download files with error: fatal: path not found: \admin1/ajax-tab.php
  7. Ok, I did a test. I cloned my live shop and used successfully the coreupdater. I went from V1.08 to "bleeding edge". I suppose that is a version that reflects latest or the latest changes marked as stable in the devs git tree. Anyhow, I am no coder and have no clue about that. Fact is, now CSS code is the named form is shown correctly and the content editor is saving as used to. Great stuff! 🙂 Having a closer look I dig that on Jan. the 8th Petr made a fix public. So, here comes the big question. What shall I do as humble merchant? Shall I manuall update all files from GIT up to Jan. the 18th or so or shall I use the coreupdater in order to update the latest changes made public on GIT or wait for 1.09? I do not want to risk raise new errors in our shop that is for sure. Thank you
  8. Custom CSS form in Warehouse template convuluted since TB V1.08 Hello this is really nasty. Since TB1.08 I would say since I do not know for certain my form that supports to save custom CSS code for the IQUIT Warehouse theme is convuluted. Escapes and so on mess all up. That needs an urgend fix since I can not work so 😕 Example: .columns-container {\r\n min-height: 600px;\r\n }\r\n /* check if good for mobil devices. made in order to not shrink content on some pages. Boris 02.2019#revws-home .btn-primary {background-color: #83C11F}/*startseiten 50% col banner*/\r\n \r\n #iqitcontentcreator .fullheight-banner {\r\n padding-right: 0px !important;\r\n }\r\n /*#order Moreover, the content creator module gives now an 500er error. Well, since the template isn't really developed anymore and worked for years this incompatibility must habe been created by Thirtybees I supppose. Anyhow, since I am not the only one with Warehouse here I hope a solution is ready?
  9. Pedalman

    Dashboard statistic stops registering sales

    Just asking into the blue: Did you change your statuses? Don't laugh but if there is no status set that tells the db that an order was sold than...
  10. Pedalman

    Google Search Console

    Just curious, what is the branch you are in? Please do not laugh, but if you are in a branch that heavily profits from Christmas business/sales then there you go. For me, it looks pretty much like that
  11. Pedalman

    Official Mollie Module

    As already said at the moment for the last 3 weeks paylater functionality was stalled (Mollie said officially they dropped support). All other payment option are said to have received their latest 'internal updates' 3 weeks ago and no one know when they might stop working. In a nutshell, at the moment all know problems are related to the webhook 'conversation' between Mollie <--> Thirtybees exclusively for the payment option paylater/Klarna. This worked for me today as stated. So, I am interested if anyone has received paylater orders in his shop the lasts days since I have not for 3 weeks except my own order (before we had daily sells via paylater). Thank you
  12. Pedalman

    Official Mollie Module

    Hello Petr, coming back to this. I reactivated Klarna paylater in live shop and did a test order. It went positively through after I created a customer with my original adress and entered my mobil phone number and birth date during checkout test (Klarna scoring test). With eyebrowses raised I had to notice that my order was accepted by Klarna and I had successfully bought on invoice/paylater and this was registered in my backoffice. In the log appears as it does in test mode: MollieWebhookModuleFrontController::processTransaction said: Received webhook request for order 1234/ transaction ord_1234 0 0x 0 08.02.2019 So, either Molly lowered their constraints on the PS/TB test or I was just lucky or what ever... I am happy since it might be something good and may be we can use Mollie in the future! Hower, before the problems started we had orders via pay later on a daily basis. My test order is now the first one for 3 weeks! What are the others experiencing here? Are you still with Mollie or any alternatives? Still receiving or freshly receiving Mollie / Klarna paylater orders?
  13. Pedalman

    Official Mollie Module

    In a nutshell: The TB version of the Mollie module hosted on Git is old (no one should use is since rounding errors etc. come with it as far as I can dig from the GIT code progress) The Prestashop version on Mollie hosted on GIT is in active development At the moment Mollie has stalled API communication for the payment option "pay later" by Klarna. We can expect to not be informed which payment option next is going to stall. Customer support told me all payment option won't get any updates any more for the TB version. I am happily willing to give access to Petr. Hope for the best
  14. Pedalman

    Official Mollie Module

    Thank you very much Petr and Lesley for your vigorate words on our perspective with Thirtybees. I know that all this arrousal came without any heads-up and no one heralded this. And you are absolutely right we have to face the actual situation and perhaps we (you 🙂 ) can workout a solution. I think the Mollie support is willing to help out, too, since we are dependent on PaymentServiceProviders as they are dependent on us. I for my part am willing to pay for the extra time needed in form of developer hours. I profit from Mollie, if it is working, and would have to spend many hours to find and integrate an alternative solution (where the same could happen). I do not know wheather there is now in this forum or in our blog a place where we can utter our top wishes that we merchants are willing or capable to pay for.
  15. Pedalman

    Official Mollie Module

    Edwin, that is what I wanted to hint at but didn't dare to say. First, I feel betrayed that TB differs to PS for any API. I have no idea of the technical side here but I am merchant and never was told that this could happen. First, that a PaymentServiceProvider or any other service can stop supporting Thirtybees cause TB's API is obviously in some ways different than the PS 1.6 one (and I hope that I am right that this was not consciously misused by someone who publicly said he does not want to be connected to TB anymore after he spend months of his life for the TB development) and second that as you point out correctly there is deadline for the PS API development. So, I am coming back to my question if there is a technical way to simulate any API? Could Thirtybees be this "open" so we will never fear to compatibility in this way or that we can get back access to Mollie etc? ********** I am not giving anyone at the moment the blame. But as said I am shocked that a service provider that claims to support Prestashop V1.6x can block Thirtybees. On the other hand I am shocked that the maintainers of the Mollie GIT claimed that for Thirtybees users there will be no problems since! Thirtybees is compatible: Am 03.11.2018 um 13:02 schrieb info@snowycatsoftware.com: > > Dear Boris, > > I just recieved your message on my voicemail. Could you please inform me who provided you with my mobile phone number, as for it is not visible on our website? > > Concerning your question regarding thirty bees. The Mollie module is / should be compatible with thirty bees, because thirty bees is compatible with PS 1.6. > > You can find the repository here: > > https://github.com/mollie/PrestaShop > > We also set up a repository here (https://github.com/mollie/thirtybees) but it is not supported and will be removed in the near future. > > You can create an account at https://mollie.com and test the module on your development / staging environment (before placing it on your live shop) to see what it has to offer. It has many great features, a lot of different payment methods and Mollie offers very competitive pricing as well. > > Have a nice weekend. > > > Kind Regards, > > On behalf of Snowy Cat Software > > Mxxx. Diexxx