Soma

I just created/imported 45k pages for users infos in about 1min.

$rss->itemDateField is for fields and not for code! It's configurable on the module screen (default) and via API. To do what you want, give every page in the feed the date of today, you could add a property hook to Pages. So you can define what, for example, $page->myPubDate will return. Then use that property for itemDateField. So such a hook would look like this, as also shown in the HelloWorld.module example. In your template code just before you render the feed: wire()->addHookProperty("Page::myPubDate", null, "addPropertyDate"); function addPropertyDate($event) { $event->return = date(DATE_RFC2822); } Now after this code a call like echo $somepage->myPubDate; Will return the current date. SO later in the $rss code you can set: $rss->itemDateField = "myPubDate";

And once you have added a field to a template you'll see a "Context" select on top right when editing a field.

From the RSS module readme // ProcessWire field to use for item date (default=created) $rss->itemDateField = 'created';

I haven't noticed any page rank influence, as google will just ignore the redirect to /de/ as it is recognized as "language". If you look at websites we do this not domain.ch/de/ is in google but domain.ch, and the rank is on the domain and not /de/.

Thanks a lot Ryan for making this configurable. I'll later check this one out. I can't find anything on google webmasters guidelines that says this is bad. We're doing this for many many websites since years and haven't noticed anything bad SEO related. Google also says, "Make websites for the user and not for search engines". Since domain.ch isn't implicating any language to the user while domain.ch/de/ does I don't see why this should be bad. Remember Switzerland has 4 languages.

Have you enabled pagination on home template?

Have you tried turning off session challenge?

Ah I've read that but didn't get it! Surely over-engineering. Not a UI pattern that someone would recognize IMHO.

Another thing I noticed with the UI dropdown menu. Hover over "Setup". It drops down. Now move the cursor fast over the first open menu item and right back up to the top menu item. The dropdown will stay hidden. This can be annoying. It looks like this is a timeout issue with this jquery menu.

Updated a install with latest version. Just noticed the top user pulldown with the wrench, the wrench icon it switches to an eye when I hover to open the pulldown.

Thanks Ryan I will test it soon and report back. There is no "/" then. It would be "/de/".

These problems may arise when installing a module manually and then updating using modules manager. This mostly has to do with folder naming of the module. MM takes class name entered on modules directory so it's possible you named the folder different when manually installing a module. Not sure there is a good way to prevent that but if you install modules explicit with mm only this shouldn't be a problem.

Just pushed a new dev branch to my fork of Shop module with the current version of the discount module included. Working nice so far. https://github.com/somatonic/Shop-for-ProcessWire/tree/dev https://github.com/somatonic/Shop-for-ProcessWire/commit/80663d3512ff251b0f616f812645b24573e19834 If anyone interested to try to see. This is my how my cart looks:

But you don't accept, we don't even have it Well then there would be the hook for your needs

Thanks Beluga. This is just a simple discount feature and nothing to do with vouchers or anything complicated. Just a simple calculation. Thing is that most simple shops I build are only local shops and most have discount depending on total sum. So I need that feature, that's why I'm working on it. I have no plans to make a full featured thing. Further here in Switzerland we're the only country in the world that has no 0.01 amount, smallest is 0.05! So I even need a special rounding. So far I have added just a method (hookable) just for that in the discount module or maybe it would even make more sense in cart module itself. It's obvious there's many things to consider and not every shop is the same, so at least a little flexibility is helpful here.

I'm currently creating an additional shopping module type for simple discount calculation in the cart. The idea is as soon as you install this module, shopping cart is recognizing it and adds it into calculation and outputs it in the cart. The module work like the shipping cost module, but will only be needed once, so no abstract class is needed. You then can enter percent of the discount and the threshold. I need this for a current simple shop I'm building. In the past I never needed that and on first shop I built I did this by building a custom checkout. Do you think this is a good idea? Or would it be better to modularize these things more in cart/checkout so one could add them without the need to modify "core" shop modules?

Every page in PW requires a "name", it's like a ID that makes the page accessible either via a view or API too. Nothing actually to worry about, just use a generic name.

Then I would create a new template "user-order" add a single page field "product" and a datetime field to the template. Then create a new order with this template , and save it under the user page. I think you just need to allow children on the family settings on the user template.

The page field will have them in the order they were added already.

Martjin, add() works for both actually. The user template has nothing to do with template files. And as long as you don't touch wire folder you're fine upgrading.

Sorry I was too quick reading wrong on my small mobile narrow view. I think you could also file an issue on github.