renobird

Hi, The simplest method is to use a subdomain (shop.mydomain.com) for your store and then power the rest of your site with PW. Most of the time I can build the entire site in Shopify though. FoxyCart is a great option as well.

Hi Pete, that was back from October 2012, so I assumed it was pre 2.3. I'll check the latest. Thanks.

Mike & Ryan, The site looks great, and is wicked fast I've spent more time on it today than probably all my previous visits combined. Nice job guys.

Hi Ryan, This issue was previously mentioned here. I'm trying to find pages like so: $pages->find("comments.text*=SomeStringHere, sort=-created"); I get this error: Fatal error: Exception: Operator '*=' is not implemented in FieldtypeComments Running 2.3

Ryan, This is great — thank you! Quite a lot happening around here for a Sunday.

Marc, I've done a couple fairly large sites with Shopify and I'm pretty familiar with the API. Unfortunately I'm a bit too swamped for the next several months.

Wow! Looking forward to seeing the real thing once the DNS is fully updated.

cmscritic, Am I reading that correctly? http://www.cmscritic.com has been converted to ProcessWire? Edit: Nevermind, Just saw this post immediately after.

Diogo, that is true, and I probably should have show it as a container tag: <ul> <txp:article_custom category="skyscraper"> <li><txp:permlink><txp:title /></txp:permlink></li> </txp:article_custom> </ul> Either way, just as simple with ProcessWire.

gfdesign, I spent years working with TXP and still maintain a small handful of TXP sites for existing clients. You really don't need to know very much PHP to build sites with ProcessWire. Sure, if you want to build complex things, then you might need a little deeper understanding, but for most sites you don't need more than the basics. Using the example you posted above, let's compare (as closely as possible), ProcessWire to TXP methods. ProcessWire // get pages with the template "skyscraper" $skyscrapers = $pages->find("template=skyscraper"); // for each "skyscraper" display the following foreach($skyscrapers as $s){ echo "<li><a href='{$s->url}'>{$s->title}</a></li>"; } Texpattern In your page: // Get all articles with the category "skyscraper", use form "list" to display them. <txp:article_custom category="skyscraper" form="list" /> In the form "list": // for each article display the following <li><txp:permlink><txp:title /></txp:permlink></li> If you take the TXP tags out of it, there really isn't much difference. When you call a form in TXP, you are basically creating a foreach(). For creating most sites with PW you really don't need to know all that much PHP. Brush up on the basics and dive in. Ask lots of questions, there are nice folks here who are always willing to help. Oh yeah... Welcome.

I'm reporting back here, although I'm not entirely sure what happened. In addition to not being able to access /processwire, I was also experiencing some odd DB behavior. so, via command line ran: mysqlcheck --repair; While everything came back as OK — when it was done— all my issues cleared up. I had also re-uploaded the /site and /wire directories, so that may have been what fixed it as well. All I know is that something was seriously borked, just not sure what. Anyhow, back to work.

Nope. :/

I'm uninstalling all non-core modules now. no scripts that mess with page view. grr...

Hi neildaemond, Thanks. This install in a University hosting environment — I've already checked with them to see if there were any events that could be causing this. There hasn't been. I would have thought that returning a 404 would indicate a permissions issue, but all the templates seem to have the correct view access.

Forgot to mention, I've checked .htaccess too.

Hi All, I have a site that has been running fine for months, but all of the sudden I can't access /processwire anymore. Instead of loading the login screen, it returns a 404. I can log myself in via the API, and everything else seems fine with the install. I've checked permissions on both the home and admin templates, cleared the sessions and cache, and checked the config.php files. Debug is set to true—I don't get any errors. Any other thoughts?

Wanze, Ah, duh! Gotcha — sometimes I still over think things when it comes to repeaters.

Hi Wanze, I'm not sure I follow there. Don't I need to get the actual page for the repeater before I can set the values?

ah, gotcha now. Yep, you are on the right track. I do exactly that.

Sometimes I also add a loader icon next to the submit button.

Hi choppingblock, Do you mean preventing the user from clicking submit multiple times? If so, I usually just handle that with JS. $("form").submit(function() { $(this).submit(function() { return false; }); });

Welcome choppingblock.

hahaha!

Thanks Wanze, I managed to get it sorted out. $n = 1; $type = "expense$n"; $desc = "desc$n"; $amount = "amount$n"; $pm = "method$n"; $expenses = $p->travel_expense; // the repeaters foreach ($expenses as $expense){ $rp = $pages->get("id=$expense->id"); // the repeater page we want to update $rp->of(false); // update repeater fields $rp->expense_type = $input->post->$type; $rp->expense_description = $sanitizer->text($input->post->$desc); $rp->expense_amount = filter_var($input->post->$amount,FILTER_SANITIZE_NUMBER_FLOAT,FILTER_FLAG_ALLOW_FRACTION); $rp->payment_method = $input->post->$pm; // save the repeater page $rp->save(); // update counter etc $n++; $type = "expense$n"; $desc = "desc$n"; $amount = "amount$n"; $pm = "method$n"; }

Hang on. I think I understand now. I was going about that wrong.