MarcC

Sure, there are many. Let's be clear: Don't know ProcessWire exists Never had any experience with it and worry about the learning curve Don't see any books about it Don't see lots of themes for it Worry about commercial support for PW Don't know anybody who uses PW Web host doesn't offer pdo_mysql (for example) Plan on blogging and don't see much blogging info for PW Need a website for posting photos and words, and their nephew offered to install WordPress for free PW certainly has an audience that is some subset of, or some small intersection with, the WordPress audience. But comparing CMS to CMS, there are so many differences in the community alone. If your goal is to attract more of the WordPress folks, you'd probably want to identify what type of WordPress folks first, and then provide resources and communication that attract them to PW. I have to explain to about one out of three clients that I did consider WordPress before suggesting ProcessWire. To them there's a bit of a risk with this ProcessWire thing. If I mess up the job, it becomes one more pain point. "And what was this Process thing he suggested? There are ten guys in town who do great WordPress sites!" These clients usually already talked to three or four people who seem pretty savvy, and a few people around the office, and most of them said some variant of, "if somebody could set up a WordPress site for us, we could take it from there." This is because there are a lot of people who work with WordPress, understand what it can do, and who maybe aren't--for various valid reasons--aware of ProcessWire's existence. So there's some fear about ProcessWire when it comes up. Sometimes. Finally, WordPress is not just a CMS; it's a community and a business (well, Automattic is). Automattic might at some point do the equivalent of Facebook buying Instagram. They might pick up or bring on board some other really sharp CMS, and ProcessWire users, the Instagrammers of the CMS world, might start to wonder when PW is going to turn really hard in whatever the new direction is. Or maybe they should start using this new Automattic thing. You never know. But with all that said, yes, ProcessWire is an amazing tool. Fresh off of a WordPress site build myself, I have to say I can see why people are so keen to jump into building their own tools. They want something that fits better. Which is, I guess, how we got ProcessWire. Maybe the cost of the precise fit for us PW users is some chunk of audience that would otherwise come from e.g. the WordPress community.

Thanks WillyC, the host had a problem on their end and they sorted it out.

Thanks, wish I could just do that myself (urg) but it's shared hosting. I'll see what they say.

I'm working on a client's hosting account at Modwest, and I followed their instructions to enable pdo_mysql, but it's still not recognized by ProcessWire during the pre-install check. So far, here's what I've done: 1. uncommented "extension = pdo_mysql.so" in php.ini That's all they say is necessary. But PW is still complaining that pdo_mysql is not enabled. What should I do or check next? (Edit: Just confirmed with phpinfo() -- nothing. I'll continue checking with the host but let me know if anybody knows something I should try)

Blogs are just a collection of features around the "date-ordered content" idea. For example, the Tesla blog: http://www.teslamotors.com/blog-and-press-releases Features: Articles listed in reverse date order Articles show a thumbnail & linked title, byline, date, and tags listing. The sidebar shows features to show articles by tag, by date, and then there are some links. Individual articles show a date, title, byline, tags list, then the article body (text, images, videos), followed by comments. Sidebars for individual articles show social media sharing links. This is all (relatively easily) doable in ProcessWire with any kind of layout, so it's up to you and your client to decide what their blog will be. That's true, but remember that your client may be hoping that you will give feedback about what they are asking for. In my opinion, and according to many of my clients, a valuable part of my job is pointing out to my clients the common things that people always want later but don't think they'll ever want when they're first thinking about their site. The blog (or whatever they want to call it) is one of those things people always want at some point. In the space of three weeks one of my clients went from "we have a blog that we never update" to "please remove our blog" (with that why-did-we-ever-do-that finality) to "please put the blog back, but hide it from the front page of our site if we don't have any recent articles." Businesses almost always reach a point where they get frustrated if they don't have a place to display timely information about changes to their business. My short list of things people usually leave out, that they should really not neglect: Blog / news area Website search function Site map Privacy policy I will often let the discussion slide if the client is feeling overwhelmed with a cool new site with hundreds of features. If that's the case, we can talk about this stuff later when I have their fresh analytics data in hand. When even the most stubborn client sees a comparison of "actively blogging and sharing content" visitor stats vs. "just a brochure website" visitor stats, they tend to take a more nuanced view of the value of a website. I try to blog actively on my own websites so I know what kind of results they can expect from the additional marketing communication.

In Chrome v.33, I'm seeing a strange bug while using TinyMCE 3.5.8 (and 3.5.10). Here are the steps to reproduce: 1. Break an existing link 2. Re-link using same URL 3. View HTML source (or save page). Entire link & linked text is missing. I wasn't able to reproduce this in Safari or Firefox. Can anybody else confirm this behavior? I'm not sure what might be causing it, just Chrome, or something in TinyMCE, or pwlink. Thanks!

That did the trick! Thanks Horst. Out of curiosity, I'm wondering why the full path is required. Is this the thing where PHP is looking in special environment paths if no path is specified (and if so, would ./filename have worked)? Marc

Example: "Added image DETA-965.jpg"

Hi Horst, I changed the "save" line and I'm still having the same problem. Here is the current code: foreach ($gallery_images as $gallery_name => $gallery) { $p = new Page(); // create new page object $p->parent = $wire->pages->get(1085); // 1085 => /photo-gallery/ $p->template = 'gallery'; // set template $p->title = $gallery_name; // set page title (not neccessary but recommended) echo "Set title to $gallery_name."; $p->setOutputFormatting(false); $p->save(); //save page in preparation for adding images (from Ryan) echo "Saved.\n"; foreach ($gallery as $filename => $description) { $p->main_image->add($filename); echo "\tAdded image $filename\n"; $p->main_image->last()->description = $description; echo "\t\tAdded description: $description"; $p->save('main_image'); echo "\t\tSaved.\n"; } $p->save(); echo "\tSaved again for good measure.\n"; } I'm not sure if it matters, but I am running the script from within (site root)/import-images/script.php -- and that's where all the images are located, too.

I'm trying to migrate a ton of images to galleries on a website I'm working on, and everything works fine except the image files themselves are not moved to the proper Assets/Files folder. Anybody know what the problem might be? foreach ($gallery_images as $gallery_name => $gallery) { $p = new Page(); $p->parent = $wire->pages->get(1085); // 1085 => /photo-gallery/ $p->template = 'gallery'; $p->title = $gallery_name; echo "Set title to $gallery_name."; $p->setOutputFormatting(false); $p->save(); //save page in preparation for adding images (from Ryan) echo "Saved.\n"; foreach ($gallery as $filename => $description) { $p->main_image->add($filename); echo "\tAdded image $filename\n"; $p->main_image->last()->description = $description; echo "\t\tAdded description: $description"; $p->save(); echo "\t\tSaved.\n"; } $p->save(); echo "\tSaved again for good measure...not sure this is necessary\n"; }

Oh good! I think that is one of the two plugins I have installed. Thanks for the tip.

Is this OK that I am (laughingly) complaining a bit about another CMS? It's a pub and that's where people do that, right? I took on a WordPress project after 7 years of no WordPress. No surprises: exact same level of frustration. After admiring the built-in "Press This" bookmarklet feature for a few seconds, I was amazed to see these dashes holding the conceptual page model together. With sortable columns, dashes start to fly everywhere! Everyone gets a dash. After looking that over, I had a back-and-forth discussion on "where is the posts page? Maybe this page should be the posts page" and it was making me feel like I had wandered back into the asylum. I pitched ProcessWire as a backend for this project, but it unfortunately it was a decision for a different team. It's also weird how there's nothing even close to, say, $input->get->foo in WP. You have to head on over to functions.php and start writing a filter so you can capture that stuff if you need it. Oh well. I'm thankful to have learned enough PHP from ProcessWire that I know what to look for and can work around a lot of stuff that they recommend you install plugins to fix.

Nice one, thanks Marty.

I'm looking for a freelancer to help me develop a calculator feature for a website. The calculator is a financial calculator based on a working Excel spreadsheet and uses simple math, yet contains more fields than a typical mortgage calculator or similar. It is not a full-fledged calculator but works more like an interactive worksheet. Please email me if you are interested: marc *a t* marccarson.com. Please let me know about any similar work you've done (or send your development portfolio website) and I'll send you the Excel spreadsheet to get a cost estimate. The build timeline would be about 2-3 weeks, beginning about one or two weeks from today. The client has also requested that the calculator have a download-me / work-offline feature (loosely defined at the moment), and I will rely on you to suggest ways that could work so that we can communicate with the client about it early in the process. Additionally if you are a heavy ProcessWire user I am interested in exploring ways we can work together on future projects involving front-end communication with a PW back-end. Thanks!

Lovely job, Ryan! I was so close to booking a 10+ person venue for an impromptu ProcessWire gathering at Calvigny, but $52K per night just sets off my grunge alarms. Maybe the pools aren't refilled nightly or something, you never know.

That's because of ->remove($page);

Thanks, Soma. I'll check it out and get these 2.2 sites upped as soon as possible.

I narrowed it down to two browsers on that website; the default theme's upper-right save button does not work in Chrome and IE, but it does work fine in FFX and Safari. I re-tested in 2.3.0 and couldn't replicate the problem, so I think it was something else for that site/client. So far this seems to be affecting 2.2.x. I'm curious to know what the difference in the button functionality might be. One of my 2.2.x sites is not trivial to upgrade, since it is a high-traffic financial services website.

Thanks, kongondo. This is in stable, plus a few sites running 2.2.x. (Edit: this may be restricted to my 2.2.x sites) Do you think it could have something to do with the server environment? The post-save message indicates a change has been made, but my changes to fields are gone unless I use the bottom save button.

I've noticed recently that I have a number of ProcessWire installs for clients where the upper-right "Save" button no longer works. I noticed a GitHub issue about this, but it seems to have to do with third-party admin themes only. I was able to replicate the problem with the default PW theme on two separate installs. I've only seen this happen in Chrome so far, so I need to do some more testing. A client emailed me yesterday to ask if I would remove that "annoying" Save button at upper-right because she just lost a bunch of work when she went to save a page. :-( Another client, using the default PW theme, said their website is not saving changes, and I've narrowed it down to this single button. So I figured I'd raise it here and see if anybody has a lead on this issue. A client who prefers to use that button asked me if there's any solution, and I told her that the current solution seemed to be removing the button. For now I removed the button with CSS. If anybody has more information on this, please let me know. Thanks!

I like it, DDV! It's great to see the photographs of the individuals along with the information. It's strange but you don't always see photos in "this day in history"-type websites. I took a similar approach with a genealogical site I'm working on--it shows which ancestors were born in the current month, died in the current month, etc. It's just in the sidebar but I think it makes the site more fun to use. I laughed at your description of yourself bolting this all together. I've felt that way before...in the very recent past...and hopefully will feel that way again soon. Thanks for sharing.

Thanks everybody--I'll give it a shot on Monday and see how it goes. I just watched "Cloudy With a Chance of Meatballs" with my kids and now I'm dreading this job a bit--can't recommend watching that film before doing batch operations.

I have a big database full of various tables that I plan to import to ProcessWire as CSV. Each record/row has a field corresponding to an image number. Then I have a folder full of the numbered images. After importing the CSV, I am planning to import these image like so: foreach $imported_pages as $page { if ($page->image_number) { if (file exists with image_number in the filename) { //Code below from Ryan $page->images->add("path or URL to image"); //save the page $page->save(); } } } Does that look right? Thanks!

Hey Marty, does this one help? http://modules.processwire.com/modules/markup-custom-page-list/ Seems you can use custom parameters to display e.g. field labels. Sorry if I misunderstood.

Thanks, I re-read your reply and understood completely. After working through the problem table by table, I am now a big fan of FULLTEXT, and the DB imported perfectly. One website restored. I appreciate the help!