Leaderboard

I have been spending some long evenings building PadLoper. It is my personal project to challenge myself as a developer, but also something I believe ProcessWire really misses: a solid eCommerce platform. I am happy to announce, that I am not very far away from public release, so I did create a little teaser site and email list for all of you that are interested: https://www.padloper.pw/ As many of you now, I also have bunch of eCommerce modules called "shop for processwire". Those remain open source modules, but I am not actively maintaining them (like I really haven't since 2012). All the code in PadLoper is new and it's totally build from ground up. If someone wants to maintain or develop shop for processwire further, I am more than happy for that. There will be some open source components coming from PadLoper also: at least payment modules, but I might also open source the shopping cart module. Padloper released 4th October, 2015: https://www.padloper.pw/

Getting closer to the release: please all you that are interested, subscribe into PadLoper newsletter to get early access invite and discount: http://www.padloper.pw/

Ah, @horst thank you! You have stopped many hours of frustration! @nico, I wanted the output to look like this: which it now does, thanks to @horst reminding me of the concat dot in your original solution. BTW, I am very grateful to have access to such a helpful community of processwire fans. This just adds to the already very awesome experience of using processwire.

Hey @kathep, it is simply missing a dot here, that concatenate your multiple results: $reading_w_heading .= "<p><a href='$read->url'>" .... $reading_w_heading .= "concatenate me"; (more here)

It depends on what kind of payment gateway you use. If you don't have need for saving the credit card numbers in your service (for "one click checkout"), then there you don't have any need to collect credit card information in your service either. Both payment gateways that PadLoper will ship (Stripe and PayPal) asks for credit card information on their services, so using them makes your service PCI compliant (or to be exact - it removes the need from your service to be PCI compliant, since you are not handling credit card information at all). Yes - although not on the first release. I want to wait little and see how things are developing on that. I have a gut feeling that there are some more changes coming. The tax class system I have in place does already have possibility to define different taxes based on location (country & state supported). It seems that digital products was just beginning, EU will be rolling changes on all sales in upcoming years. Regardind order states: I am currently wondering this one: I found most of those statuses confusing and something where the shop owner needs to define meaning. I am looking for more specific toggles, like: - order successful / failed - order delivered / not delivered - order paid / not paid What causes me some problems are those custom situations like "returned", "cancelled" etc. I think those cases a little. Then there will be order notes also. Yes, there will be invoicing and invoice pdf (or printable html - I'll have to see if I am allowed to bundle pdf libraries in this module). Regarding bank transfers, not sure I understand? You can use invoice, where the payments go into your bank account - but PadLoper will not integrate with your bank. Downloadable products will have protected links: each link is unique per product & order, and there can be "download rules" defined - like how long it's available and how many downloads are allowed. Downloading a file doesn't require login though. PadLoper adds very little on top of the ProcessWire - so if PW runs ok on your server, then will PadLoper also.

Make sure the image field is set to 1 image only, otherwise it will be an array. You have taken the right route to get to the image field, though you don't really need to set up a separate $rating variable. $page->classification->image_field, and then add ->url to output the url echo "<img src='{$page->classification->image_field->url}' alt='{$page->classification->title}'>";

hi lauren, don't know if it is working with repeater fields, sorry - but repeaters are out anyway i think the PageTable is exactly what you are looking for and you should definitely try out this great field that opens tons of opportunities! this topic is exactly for you: https://processwire.com/talk/topic/6866-page-field-in-pagetable/ in this image from the thread above you see repeaters (top) compared to pagetable (bottom): see how much space you will save btw: looks like page field should work with repeaters?! here you go you can automatically follow topics you replied to: https://processwire.com/talk/index.php?app=core&module=usercp&tab=core&area=notifications

Yes, I am learning PHP quite fast using PW. I didn't know any before last week I think I found PW by googling for a lightweight CMS. The bloated options of the big, popular CMSs, and the limitations of certain small open source CMSs were unsuitable for my needs. I hoped there was something better. I find developing in PW quite addictive. I'm not sure if its the full control of information architecture, or how much fun php is, or the ease of use of the PW API. Do others find it addictive? Anyway, I am having a lot of fun with it.

@NorbertH: https://github.com/apeisa/ProcessUserExtended. UserGroups isn't in the directory either, so no big difference there. Also, UserGroupsProcessUserExtendedIntegration (so proud of that name..) is a module that you install by hand, so just leave it out and this should be even less of a problem. It's only a bridge between UserGroups and ProcessUserExtended

Norbert, if you don't use ProcessUserExtended, then you don't need to install ProcessUserExtendedIntegration. That will be obsolete soon anyways, since latest releases have Lister at a users page.

We should probably update UserGroups into the public and add it to modules directory. It is definitely much more stable than any proof of concept modules introduced in this topic. We are using UserGroups in multiple big sites already.

Sure, though the approach depends a lot on your needs. Are your top menu items always placeholders for grouping pages or can some of then be actual pages, how deep or complicated will your site hierarchy be and does the top menu have to reflect that somehow, etc. Assuming that this is a very simple setup (no real pages in top menu at all), one approach would be creating top menu structure somewhere else (as pages), and adding a "top menu parent" Page field to pages. If a page has this field filled, it'll be displayed under said top menu item: - Home - Who we are - About us - History - Values - Meet the Cashmaster Team - ... - Topmenu - About Us - About You - ... You'll need to write your own code to create markup for the top menu, and probably side menu (if you use one), but that's just about it. Something like this should work: echo "<ul>"; foreach ($pages->find('template=top-menu-parent, sort=sort') as $parent) { if (!$parent->numChildren(true)) continue; echo "<li>{$parent->title}<ul>"; foreach ($parent->children as $child) { echo "<li><a href='{$child->url}'>{$child->title}</a></li>"; } echo "</ul></li>"; } echo "</ul>"; Anyway, this is just a very crude and basic example, so if your needs are more complicated than that, there are other approaches that may make more sense. Path/URL rewriting might be one option, etc. In any case most likely you'll never need to change any core code

Try Google image search for "padloper". Just a guess, though, Antti might have completely different explanation for this

Hello community, This is a tiny command line node app, to print out the latest ProcessWire forum posts to your terminal. Installation Following command requires nodejs sudo npm install -g processwire-forum-posts Usage The global installation will symlink an executable script and place it in your PATH. To use processwire-forum-posts type `pwforum` on your terminal or command prompt: $ pwforum More information please refer following: NPM Directory: https://www.npmjs.com/package/processwire-forum-posts Source: https://github.com/gayanvirajith/node-processwire-forum-posts Thanks

About a month ago I announced UserGroups module, which I gave humble beginning, but Nik and Teppo really pushed forward (not sure if there is anything of my original code left anymore...). We are getting closer to initial 1.0 release feature wise, so this is good time to get more feedback from you guys. We have been focusing on finding all the different situations, where user access is defined and finding the right balance of features and simplicity. I am pretty sure there must be some cases where this module fails, so please do test all kind of combinations you can imagine and hunt some bugs! Grab the module from here and install it on big, popular and complex live site and go wild (or actually.. maybe not): https://github.com/apeisa/UserGroups/ Module is based on groups instead of roles. Idea here is that groups are something that your client can manage, but roles & permissions are not. There is no documentation or tutorial yet, but just install it - I think you will figure it soon (just create few groups, look for access tab on pages and try). Also check out this companion module that Teppo has build. It allows access management right from page tree: https://github.com/Aldone/PageListPermissions/

Hi all, Here's a preview of a Gallery photo album module I am working on (very slowly! ). Development is currently in closed beta testing. The module will consist of a backend (as seen on video below) and a frontend that is framework and lightbox agnostic, aka plugin whatever and it will still work. Features Unlimited number of albums and sub-albums (easy to query using PW API) Multiple methods to add albums and photos (including uploading images and zip files, scanning a folder for FTP'ed photos, etc) Automatic album and photo creation based on names of folders and files respectively Bulk editing (moving, deleting, tagging, etc) Manager themes in several colours A bit of eye candy Etc... This is in beta so it is still rough around the edges. Feature suggestions? Yes please Apologies the video is way too long and you might get bored toward the end...

ProcessWire doesn't even touch your css file. It handles only the part of generating the html. The css file is direcly loaded as file. The .htaccess file contains the rule to forward all real files directly (css/js/images), while everything else is taken to ProcessWire itself. # Do you have any caching enabled in the .htaccess file? I can't image anything else, after all the things you already checked. Or did you check if the upload does work as expected? Maybe there are some issues in uploading/overriding the old css file on the server.

Oh geez! Sounds like I need to get with the times! ;P The PageTable field type sounds like the way to go. Thank you SO much for being so helpful, not just in answering my question but also helping me navigate my way around the forum! Thank you

@everfreecreative, you mean besides having a cooler name? . As LostKobrakai pointed out, it's all in the first post. You can't really create a 2D/Matrix table using repeaters, since, er, the rows just keep repeating with the same thing. And if you could create one, I think you would have more overhead using a repeater to create, say a 10x100 table than this Fieldtype. To understand what the Fieldtype does, think an Excel spreadsheet with column headers and row labels whose intersections contain unique cell values (by unique I mean each table cell can only ever represent a unique combination of two factors different from any other cell). The main purpose of the Fieldtype is for storing and retrieving such values. As for Table, that's a whole different beast whose scope is far greater than what this Fieldtype does...

Yup, join the club Kathep, processwire is the only cms/cmf (that i know of) that comes with automatic php learning.

Did you read the first post here? There's an explanation for exactly your questions.

you could create redirect to the first child to avoid 404 errors and problems with the breadcrumb thing! look here: https://processwire.com/talk/topic/15-how-do-i-create-a-page-that-redirects-to-its-first-child/ and here: https://processwire.com/talk/topic/7027-making-a-child-page-the-main-page/ so the pagetree is logical - the links are working and the /about-us/ page makes no errors or deadends.... regards mr-fan

There are cases where required logging in is beneficial. But I think that most often the simplicity of "click a link and download" is what one expects. This also leaves all the stress of creating and managing user accounts etc. Orders are tied into user accounts, if buyer is logged in while creating the order. So one can create that kind of functionality if required. PadLoper won't offer it out of the box though.

For things like E-Books, logging in to download is helpful because of possible publishing restrictions. For instance, if the copyright prevents the file from being available on a publicly accessible link. Additionally, for a shopper to be able to login and see a list of their purchased downloads, complete with links, then that is good too.

The name comes from the little turtle, like Teppo mentioned. No specific reason for that name. As a father of two (soon three) kids, I know that everyone needs a name - those are pretty handy. PS: pad is also handy prefix, there will be padcart, padorders etc...

Oops - just noticed, you said your image field is called "images" but you are using the default settings for this - which look for a field called "image" (no 's' at the end.) If you try this... $settings = array( 'pages' => wire('pages')->get("template=slides")->children(), 'title_xforms' => "scale(1.0) translateY(300px)\nscale(1.0)\nscale(1.0)\ntranslateY(300px)", 'image_field' => 'images', ); ...does it fix it?

Thanks Charles - glad to hear it is working well for you. I have another brand new version for you with a LOT of new features. You can prevent creation of pages from email addresses with host names that are not in the whitelist - great antispam option You can limit creation of pages to email addresses that match registered PW users - in this case, the ability to add the page will also be determined by the user's permissions for creating pages on the selected template You can determine whether the page should be published based on the user's page-publish/edit permissions You can set up customized email notification messages when a new pages is created, including choosing who they should be sent to. The config settings should also help to see all the new changes. Please let me know if you find any problems with this new version - quite a bit changed. Also please let me know if you think of improvements to the logic of the way things are set up.

Back to BBS. I like that!

Norbert, do you refer to this module: https://github.com/apeisa/UserGroups ?

I finally got around to do some thorough testing of the new capabilities. I tested on Customized Email, Gmail, Yahoo and MSN (Outlook) and everything works great. I especially like how you treated the attachments and split out the From and email address. Thanks again for all of the enhancements.

just for the record - the selector field could also be a great option for this use-case! see macrura's tutorial on widgets: https://processwire.com/talk/topic/8635-simple-example-for-widget-management/?p=83418

I obviously would love to see this being added But it might be error prone on the input side of things. You'd have to tell the user exactly what's allowed and how to enter it. I think this needs a bit more thinking on how it can be best integrated.

yeah but a little api magic can cure that.. open up your tools or api playground and: $pp = $pages->get(1234); // page you're adding the children to the page table foreach($pp->children as $child) { $pp->page_table_field->add($child); }

How about ip_type.title?

OK talking to myself again - but at least I'm in good company I'm looking through the code that builds the PWimage plugin and gets the pages to choose images from. Namely wire/modules/Inputfield/InputfieldCKEditor/plugins/pwimage/plugin.js and wire/modules/Process/ProcessPageImageSelect/ProcessPageImageSelect.module In the former file the page_id is retrieved through var page_id = $("#Inputfield_id").val(); var edit_page_id = page_id; Since my form is living on the frontend, I don't have $("#Inputfield_id").val() because $("#Inputfield_id") is not there. Looking at the source code of the backend form, I can find this element: <input id="Inputfield_id" name="id" value="11551" type="hidden" /> Where value 11551 is the id of the page I'm on. For my frontend form I'm rendering the form with code from Soma's gist. And that doesn't render the hidden input field with the value for the page I'm on. Hence the error. Now I will go and add that input myself to the frontend form and report back here what the outcome will be EDIT: sometimes a good glass of port wine can make you see things that you hadn't seen before

$pages->addHookAfter('Page::path', null, 'hookPagePath'); function hookPagePath(HookEvent $e) { $page = $e->object; if($page->template == 'article') $e->return = "/blog/$page->name/"; } http://processwire.com/talk/topic/1799-routes-and-rewriting-urls/