Leaderboard

I created a simple blank install profile for ProcessWire. I think it has been asked for a couple times, although the basic site is something really good to start with and fast to get rid of things you don't need. However in case someone wants one here it is. https://github.com/s...ireBlankInstall PROCESSWIRE 2.+ BLANK INSTALL ============================== This is a blank site profile for ProcessWire2+. It's done using the ProcessExportProfile module. There's only the following left in this profile: Fields: - title - body ProcessWire Templates - home - basic-page Template Files - admin.php (required) - home.php (required root page) - basic-page.php (404 page) INSTALLATION ============================= Get the latest ProcessWire install package. Before you install, replace the folders /basic-site/install /basic-site/templates with the ones from this blank install. Proceed with the installation as usual.

Just pushed big update on shop module. I don't even remember everything, but here are few details: Shipping options, with additional payment costs (currently only fixed cost shipping option available, but it would be pretty trivial to build more advanced ones also) Uses cookies instead of session - I settled for 7 day cookie ShoppingStepsMarkup.module, which renders 1-5 steps to completed order Bunch of bug fixes (and probably lots of new ones introduced) Most of the fields created are now system fields, so installing this will not pollute your fields & templates. (This doesn't mean you should install this on your favourite live site - don't do that [with any module]) Updated the readme with few (well.. 12 actually) simple steps how to get this baby up and running Get it while it's hot: https://github.com/apeisa/Shop-for-ProcessWire All the feedback and testing is greatly appreciated. Thanks.

Ryan's account is very accurate and very familiar! Trying to achieve and then maintain PCI compliance is a nightmare. In my previous job I wrote and maintained an on-line shop. Because I knew the codebase intimately, fixing problems there was easy, but (even though we were on a VPS) there was a great deal that the hosting company had to do as well, even as far as arguing about false positives and really trivial stuff. I don't miss it! However, I did come across an interesting bit of reading on the subject, regarding taking a web business outside PCI scope, which may be relevant to this discussion.

I will implement paypal integration for sure. But that is something that we don't need at our company, so I need to do that on my own time. But I don't think that will take more than few hours at best. I just implemented possibility to add multiple shipping options. Yesterday I build small markup module which renders the shopping steps (1. cart, 2. information, 3. confirmation, 4. payment, 5. order complete). Also some minor tweaks here and there. I will also add option to choose currency (I am not planning to support multiple currencies, but possibility to choose what currency the shop uses will be there). Hopefully I get today all wrapped up and can commit it.

Hi, Like the title says, is there a way to check what the values were before saving, to check for fields that have changed etc. Both the before and after event now seems to get the Page object after it has been updated.

Well, my blog stadtpirat.net is responsive, too

Who, I wonder, among the PW forum dwellers, is using Readability? If you are, did you read the terms and conditions before you signed up? As I've seen readability mentioned somewhere on the forum I thought I'd download it and try it out. I don't always take time to read scroll to the bottom of some new package's terms and conditions, but I thought I would for this one as it isn't on Mozilla's add-on site and my spider senses were tingling. I am so glad that I took the time to do so. For lurking there, in the not-so-small print*1, was the following phrase... Let's just look at that again, with a little more focus... As my real name is John Connor*2, I didn't agree and promptly deleted the add-on. For those of you who are using readability, or thinking of doing so; don't say I didn't warn you. *1Really. *2 Not really.

I'm not sure the software matters so much at this point, so long as it lets us get going quickly and covers the short-term collaborative needs. The focus in the beginning should be on the editors and their short term needs. Getting the content going is a lot harder than getting the software. Content is portable. Once the content is in a good place, then we're in a good spot to put it wherever it would best serve the users (while still keeping it collaborative). PW was not designed as a Wiki, so it'll take some work to make it behave like one. That means somebody coding it before we can populate any content. I think the content has to come before the software here. (Though if the editors actually prefer to use PW as-is rather than a real Wiki, then we'll do that). If it were just me, I would probably use PW since I don't know my way around Wikis. But PW is a multi-purpose tool, and a Wiki is a single-purpose tool that designed for the exact purpose we are looking for. Assuming a Wiki is a better environment for the editors, my opinion is that it's a good way to get things going short term. Moving it into a PW-powered Wiki longer term would be ideal. That way we could maximize the flexibility of the content… even providing JSON doc feeds to live PW installs like mentioned above. If we've accomplished what we want to with the content, then converting and delivering it with PW will be the easy and fun part.

Hi and welcome! Very unusual question for a first post Does this help?

This tool looks great, I can't wait for it to be fully developed. I am looking to get started with e-commerce and would love to use ProcessWire because I love it, so this module seems ideal. I would be looking for Paypal integration—is this something that will be coming down the pipeline?

Great ideas here, but I'm still voting for putting up wiki site as a starting point. Developing something more sophisticated later on won't be much of a problem, but IMHO what we need now is first version - and we need it pretty quick, so that we can see how it starts gaining momentum. When discussing the platform choices, keep in mind that most wiki platforms are exceptionally good at handling stuff like multiple editors, access restrictions and revision history - absolute necessities if we're going to have more people producing content. My experience comes mostly from MediaWiki, though, so that's what I'd suggest. It's ugly and kinda bloated but it does get things done @charliez, that sounds great too, but wouldn't it provide some extra credibility if wiki site was running at manual.processwire.com or something similar? Though I'm not sure if this was what Ryan had in mind..

I used media queries to make a PW site responsive, at least for the iPhone. Pretty easy and fun to do. Check it out either on a mobile or simply rescale your browser. It was fun to set up and easy to do. http://www.eastsidenurseryschool.org The only thing I am not fond of is my treatment of the sub navigation menu on some pages. If anyone has suggestions I would love to hear them!

Can we also get one that comes with my next client project all set up? Thanks.

And I was not here! Very nice example of usage of ProcessWire modules. Even after months, I love it!

Haha, I knew I had to be fast, this was such a great question. I don't want anyone to believe building modules for PW is hard, it's not.

I must have You must have broken some record by becoming a "Full Member" in 4 days

Digitex, I've not seen/heard of this issue before, so thinking it may be isolated. I agree it would be good to go ahead and upgrade just in case the version had some side effect. If you can still reproduce the issue after that, let me know what PHP and MySQL version you are running so I can try to setup a similar test environment.

I don't think sharing one database for multiple pieces of software is a good idea. Lots of concerns there whether PW is part of it or not. A vulnerability in one piece of software suddenly becomes a vulnerability in all. Table prefixes have been intentionally left out of PW, and I'm of the opinion that this is something other software should phase out as well (especially WordPress). I'm guessing this is from a legacy hosting platform or a free web hosting account, and so would say it doesn't meet PW's minimum requirements in that regard. I understand the hosting part is out of your hands, but would probably suggest kindly encouraging your friend to get a $3/month web hosting account from HostGator or something, so they can have more than one database. Though it surprises me even a free host would still be enforcing that limitation as it's a magnet for security problems and tech support.