MarcC

So I tried using $page->repeater->getRandom() in some template code but it didn't seem to work. Should this work? If not, what is the recommended way of working with a single, randomly-chosen repeater item? Thanks!

Here's what I'd share: Connect with other creatives. Graphic designers, photographers, marketers, etc. If you feel like you are not at the top of the list of great web designers, that's normal. But imagine how the average print designer feels about their own web design skills. Talk to those people. Many of them already have many clients who could use websites that work. Instead of spending your time cold-contacting people you want to work for, cold-contact people you could work with. (see above) They will see the value you bring into their business. Hire a business consultant, if you can. I hired a retired tech executive. His advice has saved me from making really dumb decisions, and helped me make some really important, yet difficult decisions. I have a notebook full of this stuff. Stay in the game. Don't give up on it and call it a crappy career just because you haven't been able to develop the skills yet. Lawyers are told to take 7 years to get established. Web designers might not even need that much time! But it does take some time. Take care of yourself. You will run into stressful situations. Be sure to do the things that keep you healthy. Get exercise, eat healthy food, spend time with people you care about. Avoid: Late working nights, mind reading (guessing that your clients hate you or think you're too expensive), and meetings with people you aren't interested in working with. Plan your next day every night if you can. Ask yourself what is going to happen tomorrow that will push your 5, 10, 20 year goals ahead. This is a great way to relieve stress and help you sleep better too. Provide value to your clients. Solve their problem. If the solution is a different web designer who's cheaper, tell them that. If the solution is some cheap third-party blogging platform, tell them that. If the solution is exactly what you do, give them estimates for "small, medium, large" and let them decide how much money they want to spend. Don't drop off a solution at the door. Stay with them. Offer to stick around for the first 6 months their new website is live, and handle some of their blogging or other updates. Offer to meet with them and review their analytics. They will need your help. They don't want to fail. Write about what you are doing. Keep a blog somewhere too. Share your thoughts online. Be nice to other web designers. Anyway, about what we do: This is a great way to make a living. Keep at it. Edit: You don't have to work for an agency. You can do this on your own. I've never worked for an agency except as a student, and I thought the agency model had some pretty obvious weaknesses in terms of output. I've had a couple agencies hire me to be their web guy's web guy, which sort of points at the problem. But you can also work alongside agencies (i.e. client pays you both separately), which has brought me great results.

Well, I feel like a complete idiot. I assumed comments were stored & managed as children of the "Comments" page, but they're actually managed through a field on the individual blog post pages. So, there is no problem here...sigh. Thanks to everyone who helped me troubleshoot, and sorry to waste your time.

Sent the site information to ryan@processwire.com. Thanks, Ryan.

I should mention I'm assuming that comments go under the "Comments" page, but I haven't actually seen any written to the db yet, so I don't know. I'll test it out with children / new pages allowed. Edit: OK, that did nothing.

Hey Ryan, I checked the error log but no errors have been written since I first worked on the site. Then I enabled the redirect option, but it didn't change anything that I could see. Here's an interesting twist though. What do you think? This is from the default blog setup...

Markdown reads a bit friendlier to me. I think that's part of the reason why it's more popular. Textile uses h1. Headline for an h1, and Markdown uses # Headline #. With that said, I prefer using Textile because of its features and it hasn't fragmented the way the Markdown offerings have.

OK, negatory. Comment did not save to DB. I will check the logs.

I hit "save" on the comments field and it appears we might be in business. I will confirm shortly...

Thanks Ryan--no checkboxes are checked. "Only New" is selected, then there's an email address, then at the bottom we're giving 3 days before spam deletion. This is the PW blog setup, if it helps.

I read elsewhere that a comment-saving bug may have been fixed in the dev version, so I installed it because comments weren't saving on one of my clients' sites. However, comments still aren't saving. Anything I should do to troubleshoot? The comment notification email is sent out, which is how we know that comments aren't added to the database--they show up in an email but not in the admin panel.

I needed to set a single article's created date, so I used this code from one of Ryan's forum posts: $page = $pages->get("/news/blah/"); $time = strtotime("2012-11-15"); // or whatever date you want wire('db')->query("UPDATE pages SET created=$time WHERE id={$page->id}"); The result was a date of 0000-00-00. I went in and changed it via PHPMyAdmin. Any ideas why that would happen?

I tend to use repeaters for things like board seats, where the number is typically limited to < 30 or so, but may change slightly from time to time.

Let's say I develop a site in a subdirectory, like /newsite. Now I'm ready to launch the site and all of my TinyMCE link hrefs start with "/newsite". Is there a way to mitigate the need to go in and replace all of those with the correct address?

Ryan, thanks for your reply. There is no longer a directory called "site", as it was the previous website's location and is now gone. That's why the code is working. Fortunately I'll eventually be able to yank that code, as search engines pick up the new URLs. I did follow your directions with .htacccess but for whatever reason it didn't work. I'm not a big fan of their web host...maybe that's part of it? Dunno.

Check out this beauty: if ($page->name == 'http404') { $path = $_SERVER['REQUEST_URI']; if (strpos($path, "?it=site")) { header("Location: http://www.communityfound.org"); /* Make sure that code below does not get executed when we redirect. */ exit; } }

Thanks Ryan--I tried the 2nd, since there are files used by the templates in /site/ but that still results in a "forbidden" for people who go to example.com/site. Any idea why?

I upgraded an older CMS that was located in /site/. Google (and several address bar auto-completers at my client's office) will send people to example.com/site/ instead of example.com. What's a good way to redirect those requests without messing with ProcessWire's stuff in /site/?

Nice job, Marty. I like the eye chart photo in there. (Now I am going to have a certain stuck in my head all day)

Here, check out some vintage Ryan. http://www.ryancrame...by_ryan_cramer/ (I used to listen to his demoscene stuff when I was in Jr. High and High School ) I think ProcessWire deserves some sort of backing track for sure. Renoise is cool...have you tried Sunvox?

This is absolutely possible and is done by certain restaurants. You will need to prepare your own order form but the API is like the tortilla, makes it easier to wrap everything up if you get my meaning.

Thanks, Soma. I had even read about that technique about a year ago, but never got around to using it. So...now I will. Ha ha

I don't understand the advantage of tree root != Home. Contao is a pretty big enterprisy thing though. Speaking of CMS/CMF stuff, I thought Directus was a bit closer to what we're enjoying with ProcessWire. Interesting that they actually expose the term "table" (as in DB table) to end users though.

if ($page->parent->name = 'home') { ... Doh. Thanks Nik, mysterious API issue solved, I think.

Hey does the mobile device skin support the "Recent Topics" listing like the desktop version does? If it did that'd be awesome. I use that thing all the time.