[NLP-er]

2.3.0 RELEASED! and finally closed beta stage

What's new:
- Supports translation SEO links even without vbSEO
- Translate Google Maps (configurable) - see http://www.forum.simple-nlp.pl/infor...ogle-maps.html for demo
- Little optimizations (i.e. included only necessary things for not translated pages)
- Supports several cache cleaning strategies (optimization for really big forums) and automatically disables cache for cleaning time to avoid read/write conflicts

Hi all. New release allows to use SEO links for every one!!! Even for those without vbSEO. I testes it on 2 test forums without vbSEO - 1 with URL going straigh to forum and 1 with subdirectory in url. It's working in booth cases.

Thats why I think that SEO links should finally work for forums with vbSEO and subdirectory in URL. Not tested in this configuration - who reads this topic knows why (but I know that SEO links are working for forums with subdirectory and without vbSEO) - so I will appreciate confirmation does it works on such forums or not

I hope that I don't ask for too much and having so many great users who asked for this functionality, there will be at least one cool guy/girl who let me know about this

EDIT: CONFIRMED!!!

Also for those where cache cleaning takes too long - you can create those indexes:

CREATE INDEX dateline ON vbenterprisetranslator_cache_short(dateline);
CREATE INDEX dateline ON vbenterprisetranslator_cache_medium(dateline);
CREATE INDEX dateline ON vbenterprisetranslator_cache(dateline);

NOTE:
- If you made first installation - this is already included. Only those who made update can (but don't have to) create those indxes manually
- Those indexes can help or not (even can make it worst) it depends from your mysql version and Cache TTL setting. mySQL can choose to not use indexes if too much data is selected by where clause - in this case those indexes will made things worst because those will have to be updated during inserts and deletes. If you don't understood what I'm writing here it means that most probably you can ignore it Those who have to will understand
- When you already have filled cache, then creation of index can take long time (from minutes even to hours - depending of number of rows). So if you want create it then:
1. disable cache for this time
2. (optional) delete whole cache - in this case indexes will be made immediately. You can delete cache data manually (SQL) or change clearing strategy to last one, trigger clearing task manually (in scheduled task), and going back to normal clearing strategy.
3. create indexes (if you didn't clear cache, then create indexes one by one)
4. remember to turn on cache again

ENJOY! :up: