toplakd
-
Posts
756 -
Joined
-
Last visited
-
Days Won
42
Content Type
Profiles
Forums
Gallery
Downloads
Articles
Store
Blogs
Posts posted by toplakd
-
-
I did get the point. But module is made for showing the languages available. So if its only one, its still showing the block with available languages. The ones that are using single language should disable it along with other preinstalled modules that are not needed. There is no point of having module installed if you don't use its features. But sure module could be changed to "if 1 dont show".
Yeah, I would also like to have the installation where only updater module is installed. So one can download and install only the modules one needs.
More pointless than language block with single language is the clickable phone number on the link which which works only on phone but not on computer browser.
As that front is a demo, it would maybe be good that they would add additional languages. Maybe all that have complete front translated.
-
If you use only one language than disable the Language block module.
-
Most likely not as each country has own laws how invoices can be issued and how they need to be in accounting books. Thats the part where paid modules kick in with link from your store to your accounting program. I'm sure there are some for France region as for my country threre are at least 5 optional modules available by local developers. I renamed shop invoice to "proforma invoice". Once order is paid, I issue Invoice with my accounting program to comply with local laws.
I think none of worldwide e-commerce solutions will ever provide compatibility with all the laws out of the box in basic package. No matter if paid or opensource. Thats something for add on modules.
-
It happens to me that a lot of customers write wrong email when registering. They register with wrong email (ussualy small typo) and than order is placed. Than I get contacted through contact form (logged in with wrong email) why they don't receive updates on order. And one can't even reply to them. For those orders which are payed with paypal is not a problem, as paypal payment email delivers customer correct email address so I copy address from paypal's email and can contact them back.
So, I thought I could add confirmation email field, where customer enters his email for second time and therefore gives more attention to it in case of typo. Example is already available on changing passwords, so i made some trial/error and now its working for me on account registration Also disabled validation on second email field as 2 green's could fool one that both fields match,.
Added the lines which are between "email configuration start " and "email configuration end"
controllers/front/AuthController.php ``` // Checked the user address in case he changed his email address if (Validate::isEmail($email = Tools::convertEmailToIdn(Tools::getValue('email'))) && !empty($email)) { if (Customer::customerExists($email)) { $this->errors[] = Tools::displayError('An account using this email address has already been registered.', false);
/* email configuration start /
} elseif (Tools::getValue('email') != Tools::getValue('1confirmation')) { $this->errors[] = Tools::displayError('The email and confirmation do not match.'); / email confirmation end */} } // Preparing customer $customer = new Customer(); ```
/themes/your-theme-name/authentication.tpl ```
{* email confirmation start *}
{* email confirmation end *}
{l s='(Five characters minimum)'}```-
1
-
-
That does not work on 1.6.1.19 nor on 1.7.3.3 by default.
-
I'm not in big hurry regarding GDPR module, as I do have working (simple) solution from day 1, and its current state (on live page) is way better than what I see at local websites. But will install it once it comes, due to easier managing of rights pages and especialy if it will be able to send requests directly to back office without use of contact form.
-
It's same here in our country. With preselected options on registration fields, preselected tracking to other websites etc. No data protection by default, it's basicaly stil Tracking by default :)
Big players can afford to make missing changes once needed (fined), small players could not afford to be fined, even minimum. There are some sites that are doing everything needed. But some are just ignorant to everything, as currently in my country there is one institution covering this GDPR with 1 employee for whole country :) So chances for being under revision are minimal. Another story is Germany
Currently no one wants to disable more than neccessary (or disable nothing) until first fines set the standard of what will be looked for and what will be fined.
And installing GDPR module with rights, or establishing CMS with right is one step closer to beeing compliant. Not forgeting the policy pages and Data protection informational pages (who, what for, how long, etc.)
And then you check latimes.com and it's disabled for Europe :)
-
Are you sure? That does not work on 1.6 nor on 1.7 by default.
-
Some copy paste from other forum (ps-german section) - google translate.
The first warnings have become known, These come already from 25.5.2018. Issued warnings so far: 1. Integration of Google Webfonts (linking to Google privacy does not help) 2. Lack of privacy statement (amount in dispute 7500 Euro) 3. Wrong data protection statement (no details of the person responsible for the data protection, lack of indication of the duration of the data storage, assessment basis, purpose of the data collection.) 4. Incorrect integration of Google Analytics (optin, opt out) 5. Using Facebook Like u. Share buttons. 6. Cookies
Installing only the module won't make your site compliant. GDPR Modules are covering just one part of all needed things, no matter which module you install, there are stil steps that you will need to do on your own to be compliant.
-
It was not my intention to offend you. But debate started to go into wrong directions. Yes. Some see benefits in updater, some dont. Every function has its followers. Im sure there will be another campaigns but would like to see that there was some kind of voting involved. But no voting on things which tb team thinks that are needed and will make their life easier. They are stil doing it for free and lasr campaign was just covering little drop in the ocean of spent free hours, which they could spend otherwise.
-
I would extend the voting to a contribution voting. 10$ per vote. One could buy more votes if is needed. Each one 10$. So when one place a vote reservation could be made to his CC. After week of open voting (collecting $) the winning project would collect the money others would not be billed.
-
I'm stil there for the updater as that was the main point of crowdfounding campaign. Se personaly I think it would be nice to bring the project to its end as based on reading it's in its final stages. And also not letting the crowdfounders on dry land :)
@datakick I think one can not vote for using the resources that were raised in campaign for specific project as that would kill the whole crowdfounding meaning.
But I'm sure you would get many votes if you said: I will make free PageBuilder module if I get enough votes. You could also start own crowdfounding campaign for your module: https://www.indiegogo.com/choose-your-platform And when money is raised you can start working on something else and let the founders know that their contributions were assigned to another projects as they were overvoted :) And than let us know how long you will be considered as a serious partner by most merchants (or other developers)
just my 3,5 cents.. :)
-
Http2 is more a thing, than lazy loading is not really needed as ability to set priority makes this unnecessary (with http2)
-
You can not login to front with your backend login credentials.
-
One, who have read complete post about updater crowdfounding, understands why they decided for it. 26 have read it for sure :) and donated.
-
Exactly. So bitching over free open stuff is not nice (many do it), as they can always go towards paid solutions and bitch there :)
-
@traumflug said in Thirtybees roadmap:
thirty bees is open source, so you can't loose what you already have :-)
One can always go with paid solution E-commerce. And will also have same problems with bugs, which also take time to be solved. Sometimes even longer than on open source solutions.
-
Nice for that approach. Exactly what I wanted, that each right is easily modified in the back office within tabs.
-
I checked github and it seems module will have everything needed. With template for each of the rights. So one can nicely adopt it to own theme/needs. Just hoping one would not be able to self delete account with admin aprooval. Admin area wil also have a tab for each right so i assume one would be able to write the texts in backoffice
-
This Is how I have solved it, without any module. Little changed description in CustomerPrivacyblock, plus some small editing in contact-form.tpl. In my-account.tpl I added a link to CMS page with rights, which points customer to contact form with directions what to write when they send a request. I have this since day 1 (25.may) so no one can say I didn't do at least something in this direction.
-
And if you want to style it to your theme, you can do it through global.css
-
If you will change the texts, do it in source code, as normal cms editor could break it very quick if not careful. If you will add it to blockmyaccountfooter.tpl than do it with if $is_logged, so it wont be visible in footer for unlogged ones.
{if $is_logged} <li><a href="{$link->getCMSLink(13)}" title="{l s='My Data Protection' mod='blockmyaccountfooter'}" rel="nofollow">{l s='My Data Protection' mod='blockmyaccountfooter'}</a></li>{/if}For unregistered it is enough if you show the first CMS page, with all info on one page without links to contact form. http://thbees.alza-racing.net/info/data-protection -
Will there be option to disable cookie consent in case it's not needed ?
-
Just check the links on the button if you have your instalation in folder. if it's www.yourshop.com will be ok. If it's on www.yourshop.com/store you will have to modify the buttons link
I know it could be made better, but I'm not coder. Just trial & error.
Open your new CMS page, go to Tools/Source code, and paste this into it. Remember you will have to disable General/HTML purifier as otherwise it will not work. Disable it before you copy paste the code.
After that, edit your my-account.tpl file and add a line somewhere between links in "my-account-link-list" Do not forget to change getCMSlink number with the ID number of your CMS page.
<li><a href="{$link->getCMSlink(13)}" title="{l s='My Data Protection'}"><i class="icon-file-o"></i><span>{l s='My Data Protection'}</span></a></li>
Block languages with single language
in English
Posted
More installed laguages was ment for official demo which was linked in the first post. front.thirtybees.com That demo could be installed with all languages wgich have front translation done.