1.0.4 soon?

[SLiCK_303]

After you copied 1.0.4 over, you renamed the admin folder, and removed the install folder?

[Raithlin]

@slick_303 Renamed the folder *before*. I actually extracted, renamed, removed install, removed .yml, etc. (Vagrant), rezipped and uploaded.

I've just found the version in settings.inc.php. Searching for others in case that helps.

[SLiCK_303]

in the tb_configuration there are a couple version references too

[Raithlin]

@slick_303 said in 1.0.4 soon?:

in the tb_configuration there are a couple version references too

Looking for it now.

[Raithlin]

Log shows: PHP Fatal error: Access level to GraphNvD3::$width must be protected (as in class ModuleGraphEngine) or weaker in /home/eclecdhk/publichtml/modules/graphnvd3/graphnvd3.php on line 30

That module isn't in the new codebase. Is it third party or an old one that can be safely removed?

[lesley]

Delete it from your dev shop, that should fix the issue.

[SLiCK_303]

delete... graphnvd3 gridhtml pagesnotfound sekeywords statsbestcategories statsbestcustomers statsbestmanufacturers statsbestproducts statsbestsuppliers statsbestvouchers statscarrier statscatalog statscheckup statsequipment statsforcast statslive statsnewsletter statsorigin statspersonalinfos statsproduct statsregistrations statssales statssearch statsstock statsvisits

Thats all the old stats modules, in the new version its consolidated into one module, statsmodule, which you need to install via the BO

[Raithlin]

Worked perfectly. Thanks mate.

For the record, RockPOS still throws errors, even with the new version.

[Raithlin]

@slick_303 said in 1.0.4 soon?:

oh and delete gridhtml. Thats all the old stats modules, in the new version its consolidated into one module, statsmodule, which you need to install via the BO

Thanks. Back office and site working well. Will leave the stats module for now. Got a weird error on install.

[MockoB]

Is there any chance for 1.0.4 to be released soon? I'm asking because I contacted developer for custom theme and I would like it to be on 1.0.4 as a foundation because the new features as webp, lazy load, etc. Unfortunately I can't see any commits more than 2 weeks ...

[DavidP]

@mockob 1.0.4 has been delayed a bit as they're concentrating on the GDPR, I've just had an email with a blog about it: https://thirtybees.com/blog/thirty-bees-and-gdpr/

[Tomik]

ayyyyyyyyyy and here i was waiting for the release :(

[lesley]

It will be in the next couple weeks, we are just trying to figure out how to handle the cookie issue.

[MockoB]

Great! Thanks for the info.

[MockoB]

Great article by the way! I hope you will succeed with the initiative.

[MockoB]

@lesley you may check how they handle the cookies here, it may be of use: https://www.optanon.com/cookie-consent-manager/ Just click on cookie settings in the banner.

[DRMasterChief]

I agree to the information from Ahmed Abderraham in this discussion: https://thirtybees.com/blog/thirty-bees-and-gdpr/

There is no need to put an Cookie warning, not at the moment and not with the new GDPR. There was a special thing for Cookies for UK only, but hey.... not for the rest of EU.

[30knees]

@drmasterchief That's because it's neither based on the GDPR nor on the old Data Protection Directive, but on the ePrivacy Directive. Also, one needs to differentiate between cookies that are necessary to perform a service explicitly requested by the user (no consent required) and cookies not necessary (consent required).

Furthermore, already back in 2014, the Dutch issued a fine of 25,000 EUR for a failure to solicit a cookie consent: https://www.cookielaw.org/blog/2014/12/19/dutch-cookie-law-fine-is-largest-so-far/

[30knees]

I don't know if you're trying to say that doesn't count, but fact is that there are lots of cookie fines out there directed to private companies: http://privacylawblog.fieldfisher.com/2014/history-in-the-making-the-first-cookie-rule-fines-in-europe/ https://techcrunch.com/2017/09/11/facebook-fined-e1-2m-for-privacy-violations-in-spain/

[DRMasterChief]

Hi, sorry but i have to give this in German: lies mal hier schnell die ersten Zeilen durch, das trifft immer noch zu: https://www.e-recht24.de/artikel/datenschutz/8451-hinweispflicht-fuer-cookies.html

Es ist eben eine EU-Richtlinie die in DE aber nie umgesetzt wurde, da das bisherige BDSG das besser geregelt hat :) Ist doch auch mal schön statt daß wir in DE immer nur das andersherum kennen. Und wenn ich Kunden in anderen EU-Ländern habe kanns mir dennoch praktisch egal sein, da DE-Recht gilt. Die neue DSGV wird es etwas anders regeln, aber da genügt es dennoch wenn die Datenschutzerklärung entsprechend gestaltet ist (da muss es drin stehen was die Rechtsgrundlage ist). Ob ePrivacy umgesetzt wird ist ja noch offen....

[SLiCK_303]

maybe this line of discussion need it's own topic?

[30knees]

@drmasterchief Genau, aber wie die auch schreiben: Es ist nicht ohne Risiko, keinen Cookie-Hinweis bzw Einwilligung zu haben. Die Rechtslage in DE ist nicht 100% klar. Aber hier bei tb sollten wir m.E. eine einheitliche, europaweite Konformität anstreben.