Leaderboard

Next site is online: http://www.troltsch.de (Small Real estate company hier in Karlsruhe) No special modules, but some CSS3-fancyness (hovering images). Their old site didn't have any information, so the goal was to make the maximum out of nothing.

I don't follow Google's algorithms too closely, so someone correct me if I'm wrong on any of this, but I always enjoy talking about it. As far as I know, the words in meta descriptions aren't used at all for ranking purposes, and never have been. But they have a ton of value for user marketing purposes, since that text actually appears to the user at Google. So a finely crafted meta description can be what makes the difference in a user clicking on your site versus another in the search result pages at Google. The same goes for inclusion of keywords in path structure, which get bolded if they match the user's query, marketing to the user in yet another way (even if negligible for actual ranking). You can build a site that performs well with search engines and completely ignore the meta description. But you'll get more people clicking from the search results to your site if you use them well. By that token, the meta description's value can probably be seen as very important from a traditional marketing perspective. But I'm not a copy writer and often don't know how to compel one with words in any special way. So if I (as the developer) don't have the responsibility of writing content, I might prefer to have Google auto-generate one for me rather than trying to auto-generate one at the site. (i.e. omitting the meta description or leaving it blank). Though if there is already a summary or worthwhile sub-head field included with the content, they might be perfect for the meta description. But I don't think there's any reason to be afraid of Google's auto-generated description, unless you really have good human-written content for it. The <title> tags are even more valuable for user-marketing. But unlike meta descriptions they have always carried a lot of weight for ranking. Though if my experience is correct, Google is being even more picky about what it considers a good title tag than it used to. If Google thinks your <title> tag is trying to speak more to keywords than to the user, it's value is reduced. This has always been the case, but I think it's become more so. What always seems to work well is a <title> that forms a focused and intelligible phrase (or short sentence) that reads well to the user and uses a target keyword (or keywords if they read together) in a natural way. These details are the things that we are responsible for and are able to focus on. But ultimately, even if you do everything right on your site, 80% of search performance still has to do with what's happening elsewhere and things that may be out of our hands. Most importantly: what quality sites are linking to you and why they are linking to you. But also: how good and unique the site is (relative to others) and how long it's been around… things that tend to correlate with link quality.

Can you try something like this ... for a CentOS server, I needed to change the AllowOverride setting in the file /etc/httpd/conf.d/virtualhosts.conf httpd.conf before: Options FollowSymLinks AllowOverride None httpd.conf after: Options FollowSymLinks AllowOverride All PS, if you have a same trouble with httpd you can try tuxlite script shell to make it easy for you and your virtual hosts in feature !if you have a VPS or DEDICATED server ... i use it, all my processwire sites work great,

Ok, I figured it out. The "AllowOverride All" has to go inside a Directory stanza for the path that holds this vhost. Once I created that and added the AllowOverride All then everything works correctly.

ProcessWire can be a great back-end for any kind of user data management needs that you have. But since we're shy about generating markup for your site(s), you won't find non-administrative user and account features like you would in something like Drupal. When it gets to those kinds of things, ProcessWire takes more of a framework (CMF) role, giving you tools to manage data for the things you build. If you are building a site centered around things like user registration and profile management, you may find something like Drupal worth putting up with in such cases. But if you are like me and several others here, you'd rather build these things yourself in ProcessWire, so that you can maximize control over the function and output of them. Should you want to do it, we are here to help you through it and answer any questions as you go.

Soma had some good suggestions here. I also wanted to mention I'm planning to include json-text based exports of templates and fields in 2.3, so that you could copy/paste these things easily between sites.

Thanks for testing Diogo and Michael. I'm pretty certain there's an issue in there somewhere. It may not be consistent, but luckily I've managed to reproduce it in one case here so should have enough to go on to fix it.

You can't put php variables inside single quote string, only double quotes are getting parsed. No need to use remove(), the selector is the easiest way.

Iam using in one project Repeatable Fields inside another Repeatable Fields. Everything works find except image uploads in inner Repeatable Field. Any solution for that?

Well I've worked out where the problem lies, even if I can't fix it easily. It's the default templates. I went into the database and changed the template id on my old 404 and About pages to that of my new pages and it now works... not sure what it is about the standard templates that's breaking it though.

Ok cool, thanks for the tip arjen. I've started playing around with this, looks very interesting.

Hoï guys! thanks a lot for your great help! The links are quiet helpfull and the code just perfect ) Thank you so much for your kind and so quick help! p.s @Soma: nice to see an other swiss guy. p.s. you can tag this topic as "Solved" as I don't know how to do that.

I think you're looking for something like this: <?php foreach($page->children as $project) { echo "<h2>{$project->title}</h2><p>{$project->body}</p>"; foreach($project->images as $img) { echo "<img src='{$img->url}'>"; } } ?> $project->images is an array if the images field is set to multiple. If it's a limited to 1 image field your code would work. Or to get for example the first image from the stack, you could just access it using $project->images->first()->url;

Wow! Looks pretty amazing! I can't wait to see how I can create additional widgets I would build something like analytics integration or something similar Edit: I'm ready for an analytics module. Just need to know how P.S.: A screenshot of what I build until now: http://d.pr/i/k0s1

Here's something I never finished but what's kind of something similar: AutoUpgrade This module checks if a new version of processwire is available and if it should be it'll show a message with a link. After clicking the link it'll automatically download the new version dezip it and replace the old files. But it's still alpha so you always backup your system before running an upgrade. AutoUpgrade.zip