Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


DataKick last won the day on August 2

DataKick had the most liked content!

1 Follower

About DataKick

  • Rank
    PrestaShop Enthusiast
  • Birthday 09/12/1981

Profile Information

  • Gender
  • Location
    Czech Republic
  • Interests
    I don't build webs, I build web applications

Contact Methods

  • Website URL
  • Facebook
  • Twitter

Recent Profile Visitors

83 profile views
  1. Well, you will most probably need a module. Alternatively you can use direct sql statements and query your database, but that requires quite a lot of knowledge. My module can help you with that - you can export any data from your prestashop into csv or xml format, easily filter data, sort, etc... Look at the following video to see how your particular problem can be solved by this module:
  2. Sorry for the late reply, I was on vacation with limited access to internet. I've send you a PM.
  3. Yes to both questions. There is one notable feature that's not present in 1.7 version - if you create custom fields on products, these custom fields are not visible in product edit page. The only way to edit product custom field values is via datakick inline editing or mass update functionality. Custom fields on other record types (categories, customers,...) works fine and can be edited from standard form as well.
  4. Hello Lina, The default template for GMC really exports only those products (and combinations) that are purchasable - products that are enabled, available for order, and have sufficient quantity on stock. So if some of your product isn't listed in XML, please check that the product fulfils these conditions. These condition are applied because google might penalise you otherwise. If you wish, you can easily edit the template and remove the condition: 1) select <entry> node 2) switch to Details tab in left tab 3) remove condition This is actually very easy. When you installed the GMC template, a new custom field on Categories was created as well. This new custom field is named 'Google: Category', and is intended for google taxonomy. If you go and edit any category in your system, you will find this new field in the bottom of the form, see screenshot. If you don't want to edit all your categories one by one, you can use Mass update functionality, and associate all your categories with some google category at once. Then you can use inline editing functionality to quickly edit and adjust the association
  5. Use Reference Code. Unfortunately prestashop doesn't require this field to be set, or to be unique. But you should always strive for uniqueness, it will ease your integration with third party services. Some people send product ids as a SKU, but that's a big mistake - id's can change, for example if you delete and reimport your products from csv. Also that makes transferring to other platforms quite hard.
  6. DATAKICK the missing data platform take your prestashop to the next level Send your catalog to Google Merchant Center or Facebook ads DataKick let you integrate with any third party service there is. Increase your sales by publishing your products to Google Merchant Center, Facebook Ads or PriceRunner We have already prepared feeds for many services that you can choose from. Don't worry if your service isn't among them. It's really easy to create a new integration. Or just give us a call, and we will gladly prepare the feed for you. For free Synchronize your shop with ERP systems Do you need to export your orders, customers or stock information to external ERP or accounting software? DataKick will take care of this. You can synchronize your data in real-time or in batch mode, export only incremental changes, and more... Don't waste time editing your products one-by-one. Use mass update Great news, you can stop doing that boring and time consuming task of updating your products one by one. You can now easily change pricing, quantity or default category of many products at once, with single click of the mouse. Or you can create list of products that needs to be edited, and then simply directly update its values inside this list. You don't really need to open, edit and save each one of them. Of course, this functionality works for every record type - products are just the most common use case Discover and use data you didn't even know you own Your prestashop is silently collecting various data. How about you use these informations to drive new sales, or to better understand customers behavior? You can, for example, recover abandoned carts information and offer your customers a discount as an incentive to finish the sale Or you can find all customers that have ordered product from specific category and prepare tailor-made email campaign for them Track more information about your customers or products PrestaShop is an amazing e-commerce platform. But you can very easily get into situation when it’s just not enough for your business. One of the most common problem is its hard-coded schema. It’s very difficult to track additional informations on records like products or customers. Fortunately, DataKick solves this problem - you can create new product field to track Amazon SKU number - or create a field in category record to associate them with google taxonomy - how about tracking twitter handle for your customers? Could be useful Stop worrying about your shop maintenance DataKick can help you with common and repetitive tasks. You can set it up to - perform periodic database backup - ensure that your currency exchange rates are always up to date - regularly refresh your search index And there will be more We are always working hard on improving DataKick module. Our backlog is full of very exciting features, including XML import functionality. And the best part is that if you buy the module now you can upgrade to the new versions for free! TAKE A TEST-DRIVE We offer a fully functional 14-day free trial so you can test the software. Take it for a spin and make sure it's a great fit! Start your free trial now We also have demo account where you can try the product without installing it to your own server. SCREENSHOTS
  7. Google Merchant Centre Shopping Module

    My module can export data to GMC, facebook, or any other service. Also it has supports google taxonomy mapping via category custom fields. Give it a try, it's free
  8. The problem is this line: AND p.`id_product` IN () Obviously, product id was not passed correctly to the sql. Contact developer of poslistcateproduct module and ask them to fix the problem.
  9. you prematurely terminate the first if branch by die(1) - your code is equivalent to this if ($mail_alert->add() !== false) { die('1'); } else { die('0'); }
  10. SHA stands for Secure Hash Algorithm. Hash means it's a hash, not an encryption algorithm. Therefore there's no decryption method. The only way to get original password is to use brute force, and that could take thousands of years, depending on password length, used characters etc. The salt does not add any more difficulty here since we know it's value. If we didn't know the salt value than we would be really screwed. Moreover, hash algorithms tends to collide -> there can be many input plaintexts that results with the same hash. So, even if you find (some) plaintext by brute force, it doesn't mean you have found the original password. You probably did, but there's no guarantee. Also, wordpress by default uses md5 hash, not sha. But that doesn't matter at all. It's still a hashing algorithm. @Es Club Shop - if you want to keep your passwords, instead of going this nonsense brute force route, just hire a developer to change prestashop's authentication mechanism according to wordpress.
  11. Don't even try it. The passwords in wordpress are not encrypted, they are hashed. (the same applies to prestashop) That means that there is no other way to get plain text password other than brute force. A password with length 8, based on alhpanumeric + special characters, has 1127875251287708 combinations. If password is encrypted using md5 (wordpress default), it which could take up to 4 years to crack. If user used 9 characters in a password, the encryption would take about quarter of a millenium. it's just not possible to decrypt all the passwords.
  12. Orders Multiple Summary

    Thank you for the explanation. You can actually achieve something like this by my module. You can create list showing only products ordered after some threshold date (since last week), and order products by customer. You could also add additional filter to show only products ordered by particular customer. To make thinks even better, I would also create a new custom field on Ordered Products called 'picked'. This would be yes/no column. Whenever I pick and pack the product, I would check this field to mark the item as processed. I would also add new condition to list to show only products that were not picked yet. So the result list would look something like this:
  13. Orders Multiple Summary

    What is the reason you want to do that? Maybe if you describe the problem you are trying to solve we could offer different solution. For example, if all you need is a list of products that were ordered today, then my module could help you.
  14. Well, how do you import your data? As csv? If so, than the passwords will be hashed once more - csv import expects plain text password, but you are providing already hashes. To overcome this, just (temporarily) edit file controllers/admin/AdminImportController.php and delete lines 2040 - 2401 // delete following if ($customer->passwd) $customer->passwd = Tools::encrypt($customer->passwd); Then reimport your csv file and it should work, hopefully
  15. I've just checked authentication process on both and and it's the same - password is stored to db as md5 hash salted by _COOKIE_KEY_. Nothing else. So the process you described in your original post must work, unless: 1) you use some custom code to handle authentication (some module or override that adds additional security or whatnot) 2) you didn't copy value of _COOKIE_KEY_ correctly (I bet this is the problem) 3) password value in db password weren't coppied correctly (for example, there may be an invisible space at the end) You can verify the hashing algo using following query. I have customer with password == 'password', my _COOKIE_KEY_ is s2cV9T6YzSm1hH18Bvqrdiv3UNIGted6Czvn4sqkavtd80D28pM2YIiY SELECT email, passwd, MD5('s2cV9T6YzSm1hH18Bvqrdiv3UNIGted6Czvn4sqkavtd80D28pM2YIiYpassword'); +--------+----------------------------------+-------------------------------------------------------------------------+ | email | passwd | md5('s2cV9T6YzSm1hH18Bvqrdiv3UNIGted6Czvn4sqkavtd80D28pM2YIiYpassword') | +--------+----------------------------------+-------------------------------------------------------------------------+ | a@a.cz | fd8e8bf54bf006c881d2cb4982cab953 | fd8e8bf54bf006c881d2cb4982cab953 | +--------+----------------------------------+-------------------------------------------------------------------------+ As you can see, the generated hash is the same --> hash depends only on _COOKIE_KEY value concatenaded with plain text password.