[Setting up elasticsearch module]

@violinparts said in Setting up elasticsearch module:

I believe it will be annoying to many users. Something that needs to be fixed by TB quickly.

Doesn't show up though on Safari.

Here is a fix for the space %20 issue:

1) edit /modules/elasticsearch/views/templates/hook/vue/results.html.tpl

Find: {l s='Search:' mod='elasticsearch'} <strong>%% query %%</strong>

Change to: {l s='Search:' mod='elasticsearch'} <strong>%% decodeURI(query) %%</strong>

2) edit /modules/elasticsearch/views/templates/hook/vue/main-search.html.tpl

Find: :value="query"

Change to: :value="decodeURI(query)"

3) Clear cache in your BO (performance page).

Please note that you may need to implement these changes on the same files but in other folders if you use a supported theme other than the community theme. So, for example, if you use warehouse theme (which is supported), edit the same files in the warehouse theme folder of the module (eg. modules/elasticsearch/views/templates/themes/warehouse/hook/vue)

Hope this helps. :)

[Is thirty bees dead?]

@dynambee said in Is thirty bees dead?:

There are PS1.6 modules available for elasticsearch. One is free and one is very expensive. Neither is as good as what @mdekker created for thirty bees.

I could find 3, all paid (yeah, not cheap), but at least one of them seems pretty impressive to me, with cron options and additional features: https://addons.prestashop.com/en/search?search_query=elasticsearch

Why do you think none of them is as good?

[Is thirty bees dead?]

Based on my tests, this full page caching built into thirtybees is not so solid, quite buggy (will post a github issue when I gather all the details), so I wouldn't rely on using that feature if I were you. EDIT: But, as pointed out by others here. TB is already quite speedy even without it.

[Setting up elasticsearch module]

Yeah, I agree with you about this and about the need for a cron or a hook/function to auto index new products upon or after submission, but unfortunately the only developer who worked on the module is currently absent. Hopefully one of the expert developers here can assist with that.

[Setting up elasticsearch module]

Indeed it does :)

[Setting up elasticsearch module]

Oh I thought you mean it happens while typing. Yeah, I can reproduce your issue after submitting (pressing enter)

[Setting up elasticsearch module]

If you never use the "manufacturer" attribute, I assume you can use your "manufacturer" field as "brand" by putting the brand names you sell in there when you add or update products. That should work, at least as a sufficient workaround. As for the 20%, I don't have this issue on my installation and I don't see it on your website either: https://rackmetro.com/#q=pop%20movies

[Setting up elasticsearch module]

Thanks @violinparts @dosbiner I have installed Elasticsearch version: 5.6.10 and it now indexes fine in the BO. I think it's extremely important to write that it is only compatible with ES v5 and is not compatible with v6, both on the module download page and inside the module page itself (in the BO).

[Setting up elasticsearch module]

[removed]

[Setting up elasticsearch module]

elasticsearch version 5.4 is for php 5+. My server is php 7+, so can't use that version. Interestingly the above github issue reported has also tried using ES versions 2.4.6 and 5.6.7, with similar results to mine. Also my TB is 1.0.6, not 1.0.4, although I don't know if the issue is with the TB version itself.

[Setting up elasticsearch module]

Which thirtybees version?

[Setting up elasticsearch module]

Note that I am using Elasticsearch version: 6.3.2 for php 7+ I think some things changed in Elasticsearch since version 5, but I am not sure if the module is meant for version 5 or 6 or both or if this issue is related at all.

Would appreciate any help.

[Setting up elasticsearch module]

My XHR result shows: { "success": true, "indexed": 0, "total": 8, "nbErrors": 8, "errors": [ { "id_lang": 1, "id_shop": 1, "id_product": 1, "error": "failed to parse [activeproperty] Failed to parse value [1] as only [true] or [false] are allowed." }, { "id_lang": 1, "id_shop": 1, "id_product": 2, "error": "failed to parse [activeproperty] Failed to parse value [1] as only [true] or [false] are allowed." }, { "id_lang": 1, "id_shop": 1, "id_product": 3, "error": "failed to parse [activeproperty] Failed to parse value [1] as only [true] or [false] are allowed." }, { "id_lang": 1, "id_shop": 1, "id_product": 4, "error": "failed to parse [activeproperty] Failed to parse value [1] as only [true] or [false] are allowed." }, { "id_lang": 1, "id_shop": 1, "id_product": 5, "error": "failed to parse [activeproperty] Failed to parse value [1] as only [true] or [false] are allowed." }, { "id_lang": 1, "id_shop": 1, "id_product": 6, "error": "failed to parse [activeproperty] Failed to parse value [1] as only [true] or [false] are allowed." }, { "id_lang": 1, "id_shop": 1, "id_product": 7, "error": "failed to parse [activeproperty] Failed to parse value [1] as only [true] or [false] are allowed." }, { "id_lang": 1, "id_shop": 1, "id_product": 8, "error": "failed to parse [activeproperty] Failed to parse value [1] as only [true] or [false] are allowed." } ] }

[Setting up elasticsearch module]

This seems like the same or similar issue as this bug report: https://github.com/thirtybees/elasticsearch/issues/56

[Setting up elasticsearch module]

I have completely removed TB installation. Installed again the same way (via softaculous, TB 1.0.6). Logged in to the BO without changing any setting. Logged in via SSH as root to re-confirm elasticsearch service is running. Installed the module (this time without doing the composer.json steps). Tried clicking the index buttons, same problems as I wrote above.

Does this module work for anyone on a fresh 1.0.6 installation?

[Setting up elasticsearch module]

I had to install and start the service as well. Followed the instructions here: https://www.elastic.co/guide/en/elasticsearch/reference/current/rpm.html Tested in SSH using curl 'http://localhost:9200/?pretty' and it seems to be running fine Now in the BO, when I click the "reindex" button, the rotating circle just rotates endlessly. Checking chrome console log, it shows a non-stopping loop of XHR finished loading: GET "https://..../index.php?controller=AdminModules&token=6c77f5aa67344cd534ce5135a352fdd5&configure=elasticsearch&tab_module=front_office_features&module_name=elasticsearch&ajax=1&action=indexRemaining".

Am I doing something wrong?

[Setting up elasticsearch module]

I run a dedicated CentOS 6.9 server with cPanel/WHM, self managed. I assume you already had it pre-installed, so no worries, thanks anyway. If anyone can explain the full installations details, I'd appreciate it. I already followed the instructions here: https://github.com/elastic/elasticsearch-php Added the entry to thbees/composer.json ran composer update It seems to have installed it, but when I go to the BO, and click "Full reindex" it says "Unable to connect with the Elasticsearch server. Has the connection been configured?" The connection is pre-configured on "http://localhost:9200" Not sure how to proceed.

[Setting up elasticsearch module]

Thanks. Got a link and installation instructions of that PHP client?

[Setting up elasticsearch module]

Where can I find the documentation explaining how to setup the thirtybees elastic-search module?

Thank you

[Is thirty bees dead?]

@lutek said in Is thirty bees dead?:

@nickon said in Is thirty bees dead?:

elastics module

I do not agree with you. We divide the stores into tiny, medium and large ones. I know Prestashop from version 1.2, I'm still in version 1.6.x My store is growing strongly, currently this year I can have up to 30-40k of products. Elastic search is one of the main arguments of migration, why? Speed, expandability with real product recommendations! This means growth in sales for me. Of course, I am a developer and I can handle technology. Not everyone will benefit from elastic search, but as a medium store I am more willing to support the project financially than those who only want for free. Crowdfunding for such modules is the best option.

I am more worried about the pace of development, for me the migration of my eco system is 1-2 months of work. So a lot of time investment. I have not done migration tests yet, but I am looking at the project for quite a long time. From my perspective, the online store is just the front of the entire system. Ordering, customer service happens elsewhere.

Why do I think about thirtybees? - cache of entire pages (currently the store supports two servers behind the load balancer haproxy) for redis. - elastic search - tests - source code

I also believe TB is a great alternative to PS 1.6 (and a step forward), but Just out of curiosity, aren't there available (paid) PS 1.6 modules for elastic and full page caching?

[Critical advice for TB staff.]

@rubben1985 you have to remember that most developers are not very good in business or have a good business sense and most business people are not very good at software development or have at least a good development logic so don't worry about every forum comment directed at you. I know the word "proud" was probably not the best here and I agree with you that software development is not the only way to contribute. I guess what this project needs the most at this time (except for money) is a lead who got a great business sense, very good programming background and programming logic and who is easy to get along with and can inspire & motivate people. Not an easy or cheap commodity to find.

[Critical advice for TB staff.]

@rubben1985 said in Critical advice for TB staff.:

Yes, I know, that is the reason why they should think about increasing the team with people as every startup does. It was not a demand at all but I see your point. It is true that seems that.

Yeah, that's what I was trying to explain. They do think about enlarging the team, but - not enough money. Thankfully, there are still some great community members that help, as @wakabayashi mentioned, but that's hardly enough.

[Critical advice for TB staff.]

Don't worry about the language, I am not too emotionally involved with the project, unlike others, so I can respond to the essence rather than the tone, but you should watch out when you write such posts, because, as @lesley pointed out - they may have the opposite effect (negative effect). I am sure that your intentions are good and that you posted this because you really do care a lot. In fact, I think all of us active members here care about this project or else we wouldn't be here.

So as you can see, you are also busy and can't help, so you should understand the situation and be more gentle with requests ("insist/demand"), as the team here is also very busy. Again, I do agree with some points you made nevertheless.

[Critical advice for TB staff.]

In addition, similar to magento that has one CE and one ENT.

[Critical advice for TB staff.]

Let me be the one to answer you here, as I guess @lesley might not be too motivated to answer each point you made for obvious reasons, and I think some points are good points indeed, despite the harsh language. I assume you wrote this post publicly and did not send it privately because you also wanted the community to read/support your opinion (or get community feedback), which is a valid reason, I guess, especially for a software that says that it's made for its community and emphasized they want to listen to what its users say.

@rubben1985 said in Critical advice for TB staff.:

Hi guys,

Congrats because development rhythm has improved for some weeks. Said this, I will insist on something: you need URGENTLY marketing people on board. Really, this is not an opinion but a reality and I says this because this CMS is really great and could have an excellent feature but not like this, not only with technical development. You can be sure of this. Some advice (some of them I already told once)

• Put in the team someone of marketing and UX. Forget about doing it yourselves. The actual website is HORRIBLE. It is difficult to see useful info and difficult and not intuitive to look for. It is years behind actual tendencies... Don't you have money? well, give a piece of TB to a marketing and UX agency/freelance in exchange for taking care of this area.

I agree that this forum software isn't the best for this kind of project. phpBB is a great bulletin board and it could be a good idea to consider it or a similar alternative, if it is not too hard for the team to set it up. TB really does not have enough money and manpower at the moment to do everything. They are currently mainly a 2-men show (not counting Michael, who is on a long leave right now). I am not really sure what you mean by "giving a piece of TB" exactly. If you know a good UX agency or freelancer, please let us know and let us know what piece of TB they want. :)

Just an example that leads me to write about this again. I rode a post about elastic search. It has been a hell to find the module and the only way has been through Indiegogo that has 1 one link that takes you to a post blog that has a link that takes you to github. I did not find another way!!!!

I am not really sure (and I guess most readers aren't) what this elastic search story is all about. Care to explain?

Another example: when a merchant come to the page and want to explore the advantages, disadvantages...what they look for? A list of best features, some page comparing solutions (PS vs TB, Magento,....) to show them why they should choose you......and modules and themes!!!! Do you know that majority of the people is going to ignore what is a marketplace? Dont you believe me? ask for random merchants, not technical ones (the majority of the community). Instead of marketplace create 2 sections of "themes" and "modules".

• https://thirtybees.com/features/ Is this the best way to show features? A lot of text with some icons? This is boring. Where are the images? You are doing the opposite of all marketing tendencies.

I think this is a good idea overall, but as you know, the current 2-men team can't do everything alone. Can you, or maybe someone else create some good professional mock ups for that? (if @lesley is ok with that?) This can be a good starting point. As for the comparison chart, this is not a very complex thing to do and I already did emphasize its importance just 1-2 days ago.

I was going to write only a couple of things but I will continue.

• I said it one and I repeat it. Change the home page. It is not beautiful designed, use of colors and photos are not good. An please.....do not use Wordpress....that is totally out of place if you are selling your own platform.

• If you are in the forum you can not go to the marketplace to buy a module that pleased you.

• the marketplace is not good looking at all. Not user-friendly (it is like a repository)

• new versions realeses not visible in the home. New version should be one of the first things people see as it transmits the image of things improving and being a dynamic CMS.

• include more shops using TB (specially having a good design). You can include mine if you want. The design is not bad (neither perfect) and in about 2 weeks it will be much better when we launch the new version.

• Marketplace->themes is empty!!!!!!!!!!!!!!!!!!!!!!!! Really???? This is horrible. What about compatible themes like panda? Do not they have time to create the "product"? Create it for them! If not, just delete the section (not good but better than being empty)

• Why not include a video in the home explaining TB? An actracting video is very useful.

• I will insist: change the home page design.

Do you want to join the team and work on all the above, or help finding people that do that on a volunteering basis?

• Here there is a wonderful community but I already notice some very important contributors/active members not writing anymore or writing much less.... Do not wait until others members will do too and do not wait too much time to react and implement some of the improvement I suggested. New members are needed to replace old members with no free time to be here and you will not attract them only with coding.

Marketing is 60% of a business, even if you do not believe it.

I am sure everybody here understands how important marketing is, especially for such a project, but marketing requires a) lots of money b) manpower, and since the project has not much of either at the moment, it's not so fair to expect (or even worse - demand) as much as you do. On the other hand, it's a chicken and egg dilemma. The project won't have funds and manpower to do all the above without a large community and it probably won't have a large enough community without doing all or at least some of the things you wrote.

Prestashop was smart enough to limit its PS 1.6 support until the end of the year, which is parallel to the time php 5.6 & 7 reaches EOL. They know that once this happens, users servers will start to get upgraded to newer php versions, which will push a lot of users to upgrade to PS 1.7 Which is why (or at least one of the reasons) I emphasized how important it is for this project (30bees - a PS 1.6 advanced & more-stable fork/alternative) to iron out all the php 7.2 warnings/errors (not to optimize it for php 7.2, just to make it compatible), upgrade smarty, and keep or make it fully PS 1.6 compatible (even more compatible, which is doable) to attract all those PS 1.6 owners, as I am sure shifting to TB will be a preferred choice for those sellers than moving to PS 1.7, especially when they know that php 7.2 still has 2.5 more years till reaching EOL, a long time of peace of mind. So I do have a positive outlook for this project, but I agree that some urgent actions (including some things you wrote) are required as I have discussed with @lesley, mostly privately. Then, there is that "minor" issue of making a living and generating revenue. There are several ways and business models that can be implemented for this project to generate enough income for it to grow and succeed. One model I personally believe in the most is to keep maintaining TB as a fully PS 1.6 compatible CE (community edition with constant code updates for newer php versions that will be released), generating income from partnerships and marketplace and working on TB 1.1.x or v2 .x as an enterprise (paid) edition, which is not fully PS 1.6 compatible anymore.

Just my 2c worth.