datakick

This gave me an idea for simple module to flush cloudflare cache (via api call) when store cache is cleared.

There is really something very wrong with your site. More precisely, there is some cache somewhere that is returning non-thirtybees files. 1) Thirtybees contains notification.js file, but this file does not contains references to show_new_orders at all 2) thirtybees version of dashgoals.js javascript file contains this content on line 163: $months = $this->setMonths($year); As you can see, there is no reference to $, so the error can't be trigger. The only explanation is that something somewhere is returning old/prestashop versions of these files. Please make sure to 1) clear browser cache 2) clear server cache 3) clear any proxy server cache (nginx, cloudflare, or any other service that might be between your server and your browser)

Thanks @Briljander for your input, I really appreciate Unfortunately these use cases will be out of the scope of my module (at least for now), because there aren't any immediate triggers that I could hook to. My module can only react when something happens (record is saved to database, visitors perform some action, email is about to be sent, etc...). Here there aren't such immediate actions, it's more about state in the database. I do, however, plan to implement scheduled triggers in the future, if this module takes off. There would be a cron task that would periodically check if some condition is met, and if so then trigger action. This mechanism could be used to implement your use cases.

You are right, it's basically a smart bindings between existing hooks and some actions. Very similar to IFTTT concept, if you are familiar with. If not, this is how their UI looks like, I wanna make something similar

Hi everyone, I'm presenting you my new free module named conseqs (as in consequences). This module is based on simple idea - it allows you to execute some action when something interesting happens in your store. It's vague on purpose -- it's because there are be many triggers (new order created, product changed, page visit, product added to cart,...) and many actions (send email, raise error, log information, update record in db, send notification to slack,...) that you can combine together. This module allows you to create automations like this: when new order is created send email to my email address when product stock quantity changed, and product reference is 'mug', and new quantity is below 30, then send email when user navigates to url that contains string '/blabla' then redirect to '/blabla2' when employee logs in to back office then log this information to access.txt file when user ends up on 404 page, then log the url address before email is send, if name contains 'www.' then raise error message when customer's total amount spent is greater than 1000EUR then update customer and change his group to 'Premium customers' And much more. >>> DOWNLOAD LINK <<< Demo: you can also test this module on my demo server Licensing: the free version is limited in number of rules you can create. If you need more automation, you can purchase license and use the module without limitations.

Check that you have categories set up correctly

This type of errors occurs when ajax response contains something else then valid json. It's usually caused by error reporting emitting warnings/notices into response. I bet you have debug mode enabled. If so, then disable it, and try again. Alternatively you can forward your store to bleeding edge using core updater.

I've just tested it on latest 1.0.x and it's not possible to create customer with such lastname. It is possible in 1.0.8. So my guess is that you didn't apply the fix correctly.

1) create destination place - ftp 2) install predefined XML template for GMC 3) create schedule to generate xml from this template, and use ftp place as a destination

Create a simple module that will hook into `displayHeader`. The hook can conditionally emit any html code based on your condition. You can use $this->context->controller to determine controller that's currently handling page render, $this->context->shop to see what shop in multistore is used, $this->context->language to base your decision on selected language,...

@AndyC my module is indeed quite hard to learn. It's because it's not a one-off solution, but it's more of a framework. Once you learn it, you will be able to do almost anything regarding data export/import. I understand that people love one-off, simple solutions. Unfortunately in many cases that's not that easy. Many merchants have specific needs that these simple solutions can't cover. For example, I have heard requests like: - I would like to send only products from some category to facebook feed - I want to send different image, because the main product image does not look good in google feed - How to add google categories to my products? - I don't want feed to contain products that are not on stock (even though they can be pre-ordered) - I have 10,000 products and 500,000 combinations and my server can't generate these.... - I want to have up-to-date feed... With my module you can do all of this. And much more. But it requires some learning time, unfortunately.

CSV import functionality was put on hold for the time being. Unfortunately it's too much effort for (>2week of work) for little reward, as most merchants are quite happy with build-in csv import.

Right. FPC is fixed in upcoming version, but if you are on 1.0.8 it's not recommended to use. Correct. SSC is used only by FPC What I meant is that the SSC api is public so any thirtybees/prestashop module can use it to cache its data. I don't know about any module that do this, though. Modules usually uses smarty cache, but that's different technology.

@cdwebman Are you planning to use thirtybees Full Page Cache? If not, then it really isn't important what Server Side Cache implementation you choose. It's because FPC is the only functionality in the core that is actually utilising SSC. Of course, there may be some third party modules that uses SSC as well, but I would bet you don't have such module installed.

When visitors first come to your store, thirtybees tries to detect country and currency. It uses browser's language to do so, but this method is not very precise. Alternatively, you can enable build-in geoip functionality and use maxmind geoip database to detect country based on IP address. Unfortunately, thirtybees uses legacy (no longer supported) version of this database, so it has become outdated. If you are using Cloudflare in front of your server (as I do), you might know that cloudflare do GeoIP translation and sends this information to your thirtybees server in custom HTTP header. I don't know what database they are using, but I would it's some very expensive and up to date solution. It would be insane not to utilize this information. So I've developed a very simple module that uses this http header to set up customer's country and currency. It does so only on first pageview, when cookie does not exists yet If you are using cloudflare as well, you can download and use this module for free: Cloudflare GeoIP

Any errors in javascript console?

I'm running my production site on $5 digital ocean droplet and the speed is reasonable. But of course, it's without the fancy stuff like cpanel

This module should allow you to log in into the *last* cart. It goes through the same routine as manual log in, so the pending cart is recovered. I'm not sure what is the benefit of logging into old cart? Do you have some use case? Anyway, such functionality could be easily added, so I have created a enhancement request for that. Maybe someday I'll have time to implement it 🙂

What other things? Did you file issue or reported it here on forum??? You know that bleeding edge is going to be released soon, so this is really a best time to report bugs

Why not use bleeding edge, as this issue (and then some) is already fixed there?

parser error : Start tag expected, '&lt;' not found Looks like you are trying to import invalid XML file

This javascript file is NOT loaded during initial page load. It's loaded asynchronously later when the page is already displayed. So there's no need to worry about page load/response time in this context, as it does not affect it at all. Of course, if you want to serve this file from external CDN, you can. It will, however, make your module updates much more troublesome. To do so, 1) upload the js file to external server 2) insert new row into PREFIX_configuration table, name='REVWS_APP_URL' value='<url>'. You will need to use sql for this, there is no built-in support for that in module. It should look like this: +------------------+---------------+---------+---------------+------------------------------------+---------------------+---------------------+ | id_configuration | id_shop_group | id_shop | name | value | date_add | date_upd | +------------------+---------------+---------+---------------+------------------------------------+---------------------+---------------------+ | 353 | NULL | NULL | REVWS_APP_URL | http://localhost:8080/front_app.js | 2018-07-14 13:17:35 | 2018-07-14 13:17:35 | +------------------+---------------+---------+---------------+------------------------------------+---------------------+---------------------+ And that's it.

You can safely ignore this, as it's just warning, not an actual error. And it's already fixed in the upcoming version: https://github.com/thirtybees/thirtybees/commit/34ec660385d1c643fde2f97f4c0fdfb9585a0795

that wouldn't work, as hash part of URL is not send to the server at all. And that's also the reason why it's nonsense to modify it for SEO benefits.

Crowdfunding has definitely its challenges - first of all, you need to raise quite a lot of money for this to be lucrative for developers. Say, project like this could take 3-4 weeks, with EUR40/hour rate we are talking about about 4800-6400 - then there is the matter of specification. Who will be responsible for that? You would need somebody with product manager skills to outline the development project correctly. Everyone can interpret *module to edit orders* differently - next, you need to find a developer that can actually deliver quality product *according to specification*. Nobody wants to pay for piece of garbage - then we have maintenance. There is no real incentive for the original developer to keep the product in shape, and release updates regularly. And it's needed - look at elasticsearch module, that one definitely needs some love but there is nobody to work on in now. Paid modules, on the other hands, solves all these problems.