apeisa

Of course he edited, it's a trademark

$f->inputfield, just like soma has in his examples. Or what do you mean Diogo? Here are few more examples: https://github.com/apeisa/CustomPageRoles/blob/master/CustomPageRoles.module#L198

Thanks guys! I think I will investigate that Omnipay and look into how PW wrapper for that would work!

Maybe. Not sure. I hate settings

I am looking for some guidance about how to implement payment modules in ProcessWire. I am not looking for tutorial how to add paypal payment etc, I am thinking about in much more higher or in more abstract level. What I would like to achieve is some kind of "payment framework" of sorts. This is all pseudo code, but hopefully helps to understand what I am after: // Payment form was submitted if ($input->post->submit) { $payment = new Payment(); $payment->method = "PayPal"; // ie. "AuthorizeNet" or "PayPal" etc... $payment->currency = "euro"; // If simple one row payment... $payment->title = "Donation for new school"; $payment->value = 200.2; // If multiple rows $payment->addRow("New schoolbooks", 190); $payment->addRow("Processing fees", 10.2); $payment->process(); if ($payment->wasSuccessful()) { echo "Thank you very much"; } else { echo "Sorry, it didn't work this time"; } } I would love to use something like this. It has also been my number one reason that I haven't taken few hours here and there to implement more payment methods for my current shop module - those are just for the shop and impossible to use in other areas of PW. I would love to see more general way to manage payments. This is by no means a simple task, since payments methods are all little bit different. Some have JS-embeds, others process on server, and others redirect to payment processor etc... So looking for ideas and feedback how we should approach this. Also if there is some general PHP lib doing this kind of stuff, using it would be nice too..?

onjegolders: I feel your pain. But there are lot's of skills in web development and design that "don't get old" and learning and mastering those are beneficial now and tomorrow: design in general typography color theories coding in general drawing, illustrations usability accessibility relational databases coding patterns regexps you got the idea I used to try learn "all new things" as fast as I could. Now when I have over 6 years experience as a professional (+10 years as a hobby) I am much more skeptical about new and shiny things. Of course there are new things that are clearly beneficial (RWD, NoSQL, CoffeeScript, Mobile Apps, Node.js... list is endless), it doesn't mean that you should learn and use all of those. It also doesn't mean that your years of design/coding experience has vanished or that PHP/MySQL cannot be used in anything anymore, or that all sites should be responsive. Usually best practice is wait a little to see which of the new trends are just trends and which are here to stay for a while and proving to be interesting and beneficial for you to learn. I also recommend to read some basics about the topics that are popping from each corner: when you know what is it, you will stress about it much less: "Ah, so Node.js is basically javascript on server side, and it seems to be great in realtime apps because of some bizarre reason. Good to know, but I think that at this point I don't need to learn how to use Node in my work."

I have been thinking that simple "key=value" fieldtype would be great, with nice JS-powered inputfield to having nice UI. Repeater is (imo) overkill for that kind of stuff... and in the otherhand just having textarea with this: interests=movies, internet phone=1234678 is lacking in UI-wise.

No worries Martin. Your original question is still very valid. Has anyone else tested this - is it still possible to add repeater inside another repeater in latest dev version?

jaoler: I have bunch of translations that I haven't committed yet. Will try to find time soon to make that up to date.

Ryan, sorry, not yet. Will give it a good test run tomorrow. And big thanks for your work on this! Really appreciated.

Teppo, thanks, now it works. It doesn't work on master though: If using master branch, I do get icon but don't see the hover. Instead of JS error: Uncaught TypeError: Object [object Object] has no method 'on' Above is probably because of jQuery version. I think it is just fine to create modules like this just for latest and greatest in mind, so focusing on 2.3 should be fine. So you can forget me about even mentioning this. Now that I got it working... just WOW! Absolutely brilliant solution and implementation. Congratulations on this Teppo and big thanks for your work on this. Very solid and very nice work! I just used 10 min of my life just clicking and watching that nice flashing animation with big smile on my face. I think this should definitely be on core. Not installed by default, but definitely ship with core. And maybe pack in with upcoming 2.3 (I think it can easily wait week or two to get this beauty in). And now that we have this "proof of concept" (I also think this is much more than that) - I really like the field level of version control. Makes a much more sense than page level version control. Thanks Ryan to that UI mockup btw, it was spot on!

Teppo: settings screen works now, but when editing page I get this error: Error Call to a member function getPage() on a non-object (line 269 of /home/apeisa/Apache/Roskis/site/modules/VersionControlForTextFields/VersionControlForTextFields.module)

I can't seem to get it working on my local linux test box. Pretty much default installation. Templates and field selections are empty. "Enable for these fields" field first allowed for selections, but after revisiting the module page those selections were gone and nothing could be selected anymore. "Enable for these templates" was always empty. Fieldtype selection has these options available and nothing selected: FieldtypeFieldsetClose FieldtypeFieldsetOpen FieldtypeFieldsetTabOpen Both database tables remain empty.

If xml is simple enough it should work. If there are attributes etc it will fail. Maybe I should finish this. Thinking of making one version for json and another for xml. Or better yet, making these and csv importer working in harmony (sharing some bits of code like mapping etc).

Hi Mattias and Welcome to PW. I haven't touched in Data Import module in two years and if I recall correctly I got it working "OK" with JSON but had lot's of issues with XML. As it states on module page (http://modules.processwire.com/modules/process-data-import/) it is a non working module. I am not currently looking to finish that module, so your best bet would be building custom importer (those are fun to do and we are here to help you).

Hmm. What comes after that snippet?

Any autoload modules installed? Especially ones that hook into page save process? That code cannot get into loop, since there isn't any functions.

Is that code in template or in a module?

I think my questions are: a) are there any other kind of taxes than percentage taxes? b) is the tax always calculated in same manner? From the price or added to the price? c) any other regional issues like the one Joss mentioned?

Mr. Log is on fire!

Currently there ain't any kind of taxes on these modules. Looking forward to implement them at some point. Just no clue how they should work that it would be flexible around the globe.

I have nice module to share to make users list more manageable with 1000+ users. I don't remember if I have released it yet though (and on mobile now).

Ah, sorry. This is where the problems come from. For some reason it parses the settings differently. Try to debug these: https://github.com/apeisa/Thumbnails/blob/master/InputfieldCropImage/InputfieldCropImage.module#L76 What you have on $crops after line 76? What you have in foreach? And finally why it leaves $prefix empty.

Looking at the code now... simplest solution to the error you are getting seems to be that you are calling it without a thumbnail, like this: $images->first()->getThumb(); https://github.com/apeisa/Thumbnails/blob/master/FieldtypeCropImage.module#L47

Is it different OS?