apeisa

Andrew, I don't think that what you have on your template file has anything to do with problems on saving the page on admin. But custom modules might always be a reason. If they are autoload modules (like many are) they run on every page load. How did you migrate? With profile exporter? If that is the case, then those two new fields are first ones created on your current host. Might be something related to mysql user permissions...?

Does other pages work fine? Do you have any custom modules installed? Did you migrate from another server or developed? Localhost or server? Do you run other PW-sites without a problem on your server?

On upcoming ShoppingCheckout module I have quite few settings options. I thought that I get much nicer UI by providing some fieldsets there. I had quite a few debugging sessions to figure why my values didn't save. After first save they were there, but after you visited module again they were back to defaults. I have the usual $fields as InputfieldWrapper(); Then this is working code: $field = $modules->get("InputfieldText"); $field->attr('name', 'confirmationUrlSegment'); $field->attr('value', $data['confirmationUrlSegment']); $field->label = "UrlSegment for confirmation step"; $field->description = "This is only shown in the url."; $fields->add($field); But this is non-working code: $urls = $modules->get("InputfieldFieldset"); $urls->label = "Url segments"; $urls->set('collapsed', Inputfield::collapsedYes); $field = $modules->get("InputfieldText"); $field->attr('name', 'confirmationUrlSegment'); $field->attr('value', $data['confirmationUrlSegment']); $field->label = "UrlSegment for confirmation step"; $field->description = "This is only shown in the url."; $urls->add($field); $fields->add($urls); (I have more those UrlSegments, but simplified this with having only one). The UI and first "save" works nice, but somewhere there is problems that doesn't actually save the values.

That url is ok, it shows that # also right after hitting save, and removes it when redirect happens.

Nope, no ideas. What is in your address bar when you see that 404 page?

Great idea, should be simple enough to do. I could look into that when I find time.

http://processwire.com/talk/topic/958-repeatable-fields/ And welcome Wes!

Hmm, gotta admit that I haven't thought about that at all. I think new role needs access to /admin/pages/image-crop/ and it will work. I need to get custom access easier, maybe with new permission for cropping.

Hi RTurala and welcome to forums. If you are using demo site, then look for line 90 on head.inc: <?php echo htmlentities($input->whitelist('q'), ENT_QUOTES); ?> and change it to <?php echo htmlentities($input->whitelist('q'), ENT_QUOTES, "UTF-8"); ?>

If you edit only some other field than textarea, like title field, and hit save? Does it work? If it works, it feels like tinyMCE/other js is messing with save button or something like that...

Thanks for the feedback Soma. Shopping Cart I think we need to wait for repeater to ship and see how it works with variations. I have a feeling that it will be the best way to implement variations. Shipping costs: are you thinking about per product shipping or per shipping method chosen? Or both? I think shipping stuff is something I need to focus soon. Checkout All those checkout stuff like having only fullname, email, address are just for quick developing, nothing final there I am currently doing bunch of fields and having settings to set those as visible / hidden / required etc. After that I will build custom validation for those... I am also thinking about possibility to extend those with some custom fields. I think I'll add payment_id, and if other stuff is needed to save from payment service, all those will go to one textarea field. I don't think we need anything custom here. This is the hard part, since Orders Management need to know how to use orders: if we make orders "dynamic", it will mean a lot of new code to orders management also. About what should be hookable etc I think that this is little bit hard since this is still so early and lots of moving parts. After we are more ready with very basic requirements, I think it will be much easier to see what are the pain points that many people would like to customize. Some things we already know (like what information to ask from customers) etc.

About variations: I think that soon it will be as simple as put sc_price field to a repeater. Tadam

Thanks raydale! Yes, I am trying to keep it as simple and streamlined as possible. I think that PW makes it easy since I don't have to touch the front end / product catalog at all. I think few features that I am thinking of that should be in "core" implementation, but I haven't touched at all yet: Currencies (I think first just that you can choose the currency, later maybe multiple currencies) Taxes Stock levels (should support variations) There should definitely be a PayPal gateway as a module. I am not sure if I will build that, since I cannot add any hours from my day job into that (we don't need paypal with our customers), but I really don't think that it can take many hours, so I could do that at some point. I will build Finnish bank gateways first and one local integrator (www.verkkomaksut.fi). We mostly pay directly from our bank account here in Finland and many doesn't even have a credit card.

Thanks Oliver. It is actually very simple (payment methods), and I am just streamlining that code. It will be super simple to build payment methods. It was clever thing to save order (as unpublished) before payment, no need to save state etc... Also offers possibility to try paying again like week later, if you fail at first time.

Just realized that checkout steps array is just a mess. Will implement that flow much better now that I got this together.

And if someone is thinking why I save current carts in database (and not just use session) is that I would like to offer possibility for logged in users to save cart and get back to it after session is long gone. Also offer nice possibilities in future to see where people stop their shopping process (is it at checkout or even before that).

I just pushed a big update. I did some more refactoring and have renamed the old modules: ShoppingCart ShoppingOrdersManagement ShoppingCheckout (You can now choose from all the installed payment methods which one to use.) And now there is one new module included: PaymentExample (which let's you choose: I have already paid / Send me an invoice) There is still lot to do, but this is starting to take shape. Now this creates unpublished order right after you fill your shipping details. After successful payment it will be marked as published and maybe paid (depending on payment method). I haven't given any thought about which methods should be hookable, what should be default shipping details, how default checkout process goes etc... Also code needs still a lot cleaning and security stuff etc. But if you guys see something wrong in big picture, now is pretty good time to say it

That is amazing stuff, looks so good! Now back to coding everyone...

Updating to latest commit is very fast and should be safe (always backup or make a copy where you test) from 2.1 to 2.2. Just remember to update index.php and .htaccess also, other than that it is just replacing the wire folder. Also: I have had once or maybe twice in after one year of developing with pw strange issues, when selectors didn't work. Saving certain pages (like /lang/movies/ or /lang/ or / in your case) resolved everything and selectors started working. I don't have a clue why or how that occurs.

Yes, that works! Not something that I would have tried. More likely color='0'. Does parenthesis have any other uses in selectors? elmr: sorry to taking over your topic. It was too interesting

Hmm.. number=0 actually chooses pages that have no value at all (even if number is integer field). Only way that I have found to choose number fields that have explicitly set 0 as their value is number>-1, number<1 So it seems that 0 is universal and meaning more like a NULL there.

Little OT: How can I choose integer fields with value 0, but not empty? (not that I need that, just realized that color=0 does match both, empty and with value 0.

It depends on what kind of field your "color" is. If it is a textarea, integer or other "basic", then you can check it like this: color=0 If it is page field, then this will do the job: color.count=0 EDIT: Leaving it empty just like Pete and Some suggested works too,

What happens if you haven't renamed your origin and you git pull the new branch (which has only README)? I assume it will throw errors, but I am not sure.

Thanks Ryan! I didn't realize we can use same selectors there on modules too! PW surprises all the time That makes a lot of sense to me. I have never build interfaces or abstract classes before, only read and used sometimes. I agree that this is pretty ideal place to use one. This will probably end like a horrible mess, but I will try 8)