szabesz

Hi, Some ProcessWire developers already use Snipcart: https://snipcart.com/list-ecommerce-payment-gateways I am also developing a site with eCommerce capabilities, but I have not yet reached the stage of dealing with Snipcart, currently I'm building the basics (database and some templates, etc...). Snipcart supports Authorize.Net which I need and use in other non ProcessWire sites, but it also supports "European merchants" listing Paymill and Mollie. I do not know how reliable the latter two services are, but Authorize.Net is solid. And Snipcart is not only a payment provider but a lot more, so I expect that I will be able to cut down on development time considerably.

Hi, the blog works by using page()->children... etc. (see blog.php). When switching the template, the children will be the pages under Home which are not pages of blog-post templates, so there are no comments (among other things) to display. You need at least to look for the selector(s) being used by templates, and change them accordingly.

Thanks for the tip! Now I just have to decide which way to go

Thanks for sharing @clsource! Seems to be a popular topic these days. Have you seen this one?

Maybe I was the first one who tried not to do it BTW, can it be considered to be a bug? What do you – and others reading this – think, should I open a new issue for this at GitHub? Or it just the way it should be: installing all languages modules is required. Full stop

Thank you, you seem to be right! I installed the module and all the others required by it, and the label showed up. However, maybe it is just me who does not understend the description, but it sounds to be the opposite: "Field that stores a page title in multiple languages. Use this only if you want title inputs created for ALL languages on ALL pages. Otherwise create separate languaged-named title fields, i.e. title_fr, title_es, title_fi, etc." So that is why I though installing the module Languages Support is enough in the case of language-alternate fields. I do use AOS, but whenever I have an admin issue, that is the first I turn off temporarily to make sure it is not the culprit.

I must be missing something important here. Where are exactly those label setup fields? I cannot see them.

Hi @AndZyk, You mean the Default/Hungarian label of the language-alternate field called title_hungarian in Setup > Fields? If so, the answer is yes, I did provide both labels but it does not make a difference. Do you happen to have a/some working site(s) with language-alternate fields where the extra labels show up as seen int he demo video? BTW, I'm thinking of switching to Multi-language fields but that generates language variations for image descriptions which I do not need, so some simple language-alternate fields would be enough for me. cheers, Szabesz

Hi, This is the first time I'm setting up "Language alternate fields". I was following the docs, especially Ryan's demo: www.youtube.com/watch?v=eq-9GQCT0lw In the demo Ryan points out that ProcessWire should add a "little label" displaying the language being used for the language-alternate field (signaling that ProcessWire identified the field as a language-alternate one). I have setup my field as seen in the video, but the extra label is missing as you can see it in the screenshots: Any idea what is going on? I would like to see the label to make sure my setup is ok before I proceed.

userAuthSalt: " it is forever tied to the passwords as a secondary salt." But if you use the very same database and files normally you should only need to update $config->httpHosts as @Sérgio Jardim pointed it out above.

Did you also uncomment this one? # ----------------------------------------------------------------------------------------------- # 9. If you only want to allow HTTPS, uncomment the RewriteCond and RewriteRule lines below. # ----------------------------------------------------------------------------------------------- # RewriteCond %{HTTPS} off # RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

I edited my previous post too by adding this one to it:

I'm not an .htaccess guru, but I dug up this one from the forum some time ago (sorry, I dunno where it was posted and by whom): # inserted before the block "# 13. OPTIONAL: Redirect users to the 'www.' version of the site (uncomment to enable)." # ----------------------------------------------------------------------------------------------- # OPTIONAL: Redirect users to the non 'www.' version of the site (uncomment to enable). # For example: http://www.processwire.com/ would be redirected to http://processwire.com/ # ----------------------------------------------------------------------------------------------- RewriteCond %{HTTP_HOST} ^www\. RewriteCond %{HTTPS}s ^on(s)|off RewriteCond http%1://%{HTTP_HOST} ^(https?://)(www\.)?(.+)$ RewriteRule ^ %1%3%{REQUEST_URI} [R=301,L] This is for non www of course, but it works for me on cPanel shared hosting sites. I do not like www, so I never tried the opposite. EDIT: I've found the source:

Thanks @clsource. I've just hit +1 at GitHub. Anyone else to make this one more prominent over there?

Thanks for sharing! I do like the design although the heavy usage of eye candies is a bit too much for my taste. A couple of artifacts I noticed in Mac Chrome: [...old and big image, I removed it to save space...]

This is great, thanks! May I have a suggestion too? Searching by name is one thing, but what if we could search by "tags"? I mean lots of icons can be used in different contexts, and most of the time I cannot even guess the name. For example I use "Car" for the article excerpt/ledes (in a "leading the way" sense). More examples I use: Trophy => bagde, Fire => effects, Compass => sku, etc... These associations could be (hard?) wired into the module, so that you can make search possible this way too. I would be happy to contribute, or even better, you could somehow make it possible for everyone to contribute.

Just for reference, now we have (thanks @Robin S):

Maybe a color management / color profile issue? http://www.color-management-guide.com/web-browser-color-management.html I think it is still best to stick to sRGB. I do not think that with mainstream monitors we will ever be able to expect that people out there will see the "same" colors as we do on our own screen.

@Chamche First of all, ask your hosting provider to turn off ModSecurity, or they should let you know the .htaccess rule(s) that need to be added to the beginning of .htaccess. There is no need for mod_security if you use ProcessWire with the .htaccess file it comes with.

Welcome to the Forums, @Chamche Any error messages to share with us: PHP, apache? Also, what is the output in the browser?

If you only want frontend login, the easiest way to do it is using @adrian's Page Protector module. For tips on how to use it that way start reading from this post: If you want to do it all by yourself? Probably the most famous post is this one (with some deprecated functions inside, so read the topic carefully): Alternatively you can use a helper module too: https://bitbucket.org/pwFoo/frontenduser/wiki/Documentation And as @rick said, you can search the forum for a lot more examples.

Hello @Dee Welcome to ProcessWire! As stated above, it is recommended that you familiarize yourself with the "manual" (more like semi-automated) standard installation process. I wrote a step-by-step guide for cPanel, you might want to check it out: http://szabesz.hu/blog/install-processwire-in-a-subfolder-on-shared-hosting-cpanel_ins-sub/ In my tutorial I explain how to install websites running "side-by-side" from the same cPanel account, you might want to stick to it. When I'm writing about the "Regular Site Profile", just use this one instead: https://github.com/dadish/pw-skyscrapers-profile as currently this is the only easily installable up-to-date version of Skyscrapers Profile. Please read the "Warning!" in its readme to make adjustments as described (FieldtypeMapMarker dependency). The other profile I recommend exploring is the "Regular Site Profile". These two should give you an idea of how things are wired together with ProcessWire. Have fun with ProcessWire and just ask for help should you get stuck.

Sure. You can always tweak it later on if necessary.

Conceptually such a module will never be part of the ProcessWire core, however, thanks to developers there are lots of useful modules out there solving various needs such as: Think of ProcessWire as a Content Management Framework and not as a CMS. The phrase CMS is used because the ProcessWire backend is powerful enough to be called so. ProcessWire is somewhere between a CMS like Joomla and a framework like CodeIgniter. And this is done all conceptually. Those who rely on it appreciate this, that is why we are here in the first place. You might need something else, it is up to you to decide. BTW, there are similar systems out there (such as SilverStripe that comes to my mind), meaning ProcessWire is not a one-of-its-kind system at all in this regard. However it is a one-of-its-kind in its OWN category Hope this helps.

One day we will wish we had this flavor of cookie instead of what they are baking for us.