Jose J. Fernández

I have managed to do this. The Starter Theme got it right, in my opinion. You just need to edit the file /templates/_partials/form-fields.tpl, where markup for every available form field type is waiting for you to edit them.

Hi there. I am trying to modify how input tags for the login form are rendered in file /templates/customer/_partials/login-form.tpl, and found this code that generates them: {block name='form_fields'} {foreach from=$formFields item="field"} {block name='form_field'} {form_field field=$field} {/block} {/foreach} {/block} Now I want to change the HTML of these inputs, mostly to insert new attributes on them (classes, placeholders maybe... whatever). How can this be achieved?

I completely agree with your points, but I think I am not making mine clear. I'll try again: - Original sentences (English) are sometimes BAD. Remember, PrestaTeam are native French speakers, not necessarily English. - Often, translations are machine translations. They sometimes get preference over human-made translations, even on new versions. - Translations are inconsistent. Crowdin is fine. What is not are weaknesses in the process PrestaShop follows to manage translations. And that's why I am requesting participation from people in PrestaShop. I can't fix their process myself. I would have done that already.

Thanks for your comments. I've been reading the docs and it looks like Webpack will be The Tool from now on, to be honest, but as you just said little has been published in the PrestaShop community about it. Whatever I manage to find out will be published somewhere else, probably here. I still like forums better than IM. Maybe getting older or something.

Thanks for your response, I was not aware of that resource. That said, maybe there are too many places to talk about PrestaShop :|

I have already been collaborating in Crowding. It does not address the issues I am bringing up here.

Hi there, I am creating a theme for 1.7 based on the StarterTheme. I am replacing Stylus with Sass and implementing Bootstrap 3.x, and no problems so far, but things are different when laying my hands on Webpack. I just have no idea. Ideally I would replace it with Grunt or Gulp, since I have experience with them and use them fine in other projects, but I guess that Webpack is being used to include default PrestaShop Javascript. Is this true? Can I just exclude Webpack from the party or am I being forced to use it? Also, as a side note, I am not new to web development and project tooling in general. It's just Webpack that I don't know how to use. Thanks!

Hello, My name is Jose. I am a Spanish developer who works with PrestaShop quite often. I usually find issues with translations, and while there have been some efforts to solve them, I still feel that there's room for improvement. I would like to bring this topic up: the quality of original English sentences, which I feel is somewhat low. That's to be expected since the Presta Team does not have English as mother tongue, but let's just find ways to improve My questions for the PrestaTeam: How do you generate English sentences? How can we improve this process? Are those sentences kept between versions? Do they need to be re-translated when a new version arrives? I'm open to start, work and/or coordinate new efforts on this matter since I feel that this is preventing any improvement in quality of non-English translations. The community can't fix problems at this level, and from wrong sentences in English, wrong sentences would appear as a result. I still thing that we need a little more involvement from the Presta Team. I am aware of the Crowdin project and have contributed to it, actually, but the issues brought up here can not be solved with that tool. Why am I opening this: Translations can be improved. Both English and, as a result, Spanish (which is my main language). I often find the same issues with Spanish, over and over again. Previous efforts on this have gone to nowhere (at least in the Spanish community). We can improve how we use Crowdin. I want to help and make things move. I love open source and just want to contribute. Time to give back. What I am expecting: Getting to an English translation which feels natural and serves as a good starting point for all languages. Getting to a Spanish translation which feels natural. Improving the process so that everyone wastes less time re-translating everything and fixing stuff that has been already fixed. Create translation guidelines for Spanish, following with the work done here: https://www.prestashop.com/forums/topic/393702-hilo-oficialdocumentaci%C3%B3n-de-prestashop-en-espa%C3%B1ol/ Resources so far: http://build.prestashop.com/assets/ext/PrestaShop_Translator_Guide.pdf As long as we discuss and find resources or info, I'm going to keep this updated. Comments from everyone are welcome, and input from the Presta Team would be greatly appreciated. Kind regards

Para dejar de ver la información de prueba en el dashboard, hay abajo a la derecha un botón que dice "Modo de prueba"... Desactívalo. A mi me costó bastante encontrarlo

Hola, En robots.txt puedes indicar que se desindexe todo un directorio. Esto es, todas las URLs que estén dentro de /es/. La regla sería la siguiente: Disallow: /es/* Para eliminar una URL concreta, simplemente añádela así: Disallow: /78-conectores-para-tira-de-led Revisa bien en el Webmaster Tools que estás eliminando las URLs que quieres y no más de la cuenta Saludos.

It doesn't make any difference from the SEO point of view. Just take care of redirecting visitors to the version of your choice, and try to use the canonical meta tag. Whatever you choose, stick to it and avoid changes. If you changed from www to non-www or vice-versa, you must redirect every single URL in your site to avoid losing your rank in search engines. I have written an article on this topic: Why use -or not- www on your domain name (in Spanish) You would want to use www because of some DNS tricks you can use, and for some bandwidth-savings with a CDN in a subdomain, among some other reasons. You would want to stop using www mostly for aesthetical reasons

I have it. After thinking for a while I took a look at the file encoding with Notepad++. The standard modules which come with Prestashop were all encoded with ANSI, and mine was with UTF-8. So, converting from UTF-8 to ANSI fixed the problem. So fast, so good. Something about this must be mentioned in the documentation I think. Anyway, thanks for your help bellini13. Regards.

Thanks for your reply. That's what I have done. I have also tried installing the module via the "Install new module" (zip upload) option in the back office, I could be doing something wrong but even this way it triggers the error. I am using Prestashop 1.4.7.2, maybe documentation has been written for a previous version (like 1.4.6.x)? Could it be a platform (Windows, XAMPP) issue?

Yes, there is: {if $cookie->isLogged()} Hi user {else} Hi guest {/if} The blockuserinfo module had this, you could have checked it

Hello, I am new at module developing for Prestshop and just started following the official documentation site for module developing (http://doc.prestasho...estaShop+module). I copied the "MyModule" example code to a php file into the modules directory as follows: /modules/mymodule/mymodule.php /modules/mymodule/logo.gif I'm testing on a Prestashop 1.4 fresh install on a XAMPP system under Windows 7 x64. Happens that when I open the Modules tab, an error is triggered displaying this message: Which looks pretty unuseful, if I exec the file without the first if and declaring class Module {}, it doesn't throw any error. I have been searching in Google but nothing useful came from that. Also, it's the example in the docs, it must work, right? :| just in case, this is my code: <?php if (!defined('_PS_VERSION_')) exit; class MyModule extends Module { public function __construct() { $this->name = 'mymodule'; $this->tab = 'Test'; $this->version = 1.0; $this->author = 'Firstname Lastname'; $this->need_instance = 0; parent::__construct(); $this->displayName = $this->l('My module'); $this->description = $this->l('Description of my module.'); } public function install() { if (parent::install() == false) return false; return true; } } ?> Any idea? Which is the best course of action as of right now? Can't think of anything, and the error message is not helping tough. Thanks in advance.