MadeMyDay

Well, then... Try this one: https://processwire.com/talk/topic/1025-multisite/page-4#entry46652

Okay, let us start over: Which module do you use? The one from Apeisa or the Soma edition?

Hard to say... You type in hortonsshortuns.com (without www) and then you get redirected to horton-stephens.com, not to some 404 page? Do you have one (404) and are you sure you are on the homepage? You haven't changed your .htaccess I assume?

No, no. Apache has nothing to do with this module. The module only identifies the page name, does some path voodoo and that's it. No further server side configuration needed. Your mistake is that you added several different domain names in the module's configuration. So basically it has to be configured like that: - Homepage -- sub page 1 -- sub page 2 [...] -- sub site (with page name "hortonsshortuns.com") --- sub site sub page 1 --- sub site sub page 2 --- sub site sub page 3 [...] And in your module's config you only define "hortonsshortuns.com" as another domain. The www stuff should be configured with htaccess, but never ever put several domain variations in the module's config. This has to go wrong.

HTML5 Geolocation is opt-in only, so I wouldn't rely on that. First-time-visitors are prompted to a popup for accepting the auto-detect. And if your website is not self-explanatory why it needs the geolocation I'd rather use that with caution. Probably best solution is to give the visitor the choice like: WEST | CENTRAL or [auto detect location]* Then somewhere on the site give an explanation why they should accept auto-detection like "* our website offers different content dependent on your location. We can auto-detect your location, you only have to allow this once". And addtionaly start detecting only if visitor has clicked the detect button.

Yeah, the force is strong in our country

Like Soma suggested with language alternate fields installed, but for less redundance I'd go with that: three (or more depending on language count) fields: firstSliderImage (image) firstSliderImage_fr (image) multilangSliderImages (image) then you build your slider like that (shematic): $firstSlide = "<div class='slide'> <img src='{$firstSliderImage->eq(0)->url}'> </div>"; foreach($multilangSliderImages as $si){ $slides = "<div class='slide'> <img src='{$si->url}'> </div>"; } $slider = $firstSlide.$slides; echo $slider; Advantage: Your client only has to differ the first slides, for the rest it suffices to upload one version. edit: While re-reading this, it isn't even needed to build it like that since with language alternate fields you can configure to fall back to the standard language content. So just build it like Soma suggested, no need for multiple upload of the same image.

Process is always the same: 1. ModulesManager then (with the help of 1.): 2. MarkupSimpleNavigation 3. FieldTypeCropImage 4. ProcessPageDelete 5. FieldtypePageTableExtended (of course ) + Nearly every (as of today + upcoming) uses ListerPro and FormBuilder.

Man, this Cabernet, too! And you are totally right. It obviously doesn't work with the current version. Seems I broke too much last time when merging stuff. Will take a look and report back (but not tonight, see first 4 words of this posting)

Hey Joss, sorry, totally oversaw your posting. Could you give some more information (more code)? Not sure why the error is given in the image.php...

Even better

Well, I think the warmup is officially only for attendees. But there will be no entrance control (I think).

Nico... https://twitter.com/kopfnuss/status/527149266746474496

I'll be there and won't miss this thread again ;-)

Thx André. yep, both My initial need for this was to have a possibility for clients to mix different layout templates. PageTable does exactly that while keeping the flexibility of normal templates. So the functionality was there but for not so tech-savvy clients it was too less visual. They want to see what they create. So this module was born. It is now your decision if you want an exact 1:1 copy of the frontend which results in more work but a nicer Interface or if you just want them to keep track of their edits/additions. I use the module in three sites at the moment (not public yet but one is shown in the video above). I generally wouldn't promise a 1:1 view of the frontend because clients then tend to "style" the content by themselves. I have one client who always tries to fit the length of text lines in two columns. If the interface would kind of promise to be an 1:1 copy of the frontend (which it NEVER can be) it would be a false safety so I'd rather suggest to keep the layout model in this module but make no promises about exact styling.

Update: Today the last of the four sites went online. This last one is by far the biggest one: ~20.000 users, each with profile options which are searchable in this section: http://lu-web.de/lu-links/ (search for "Hannover" for example), additional options are available when "Nach Qualifikationen filtern" is clicked. Also there are eMagazines which are only viewable if the user is logged in and has an active subscription. To sum up: http://schaedlings.net http://kommunaltechnik.net http://beckmann-verlag.de http://lu-web.de

Please grab a new copy / checkout the branch again. Or just delete line 101, it made more trouble than had benefits

No, this is plain PHP. Since 5.3. I think and if short tags are activated in php.ini, which it is mostly. So <?php echo $var; ?> is the same as <?= $var ?> is the same as echo "$var". Double quotes are necessary, echo '$var' won't work. The curly brackets are for encapsulating object references or functions. echo "$image->url" won't work, while echo "{$image->url}" will.

Perhaps read the documentation first: http://processwire.com/api/fieldtypes/images/ As I said: If your image field is called "myImageField" (I actually don't know how you called it, you mix a lot of names up there ) and is set to a single image, you have to wrap in an image tag: <img src='{$myImageField->url}' alt=''> The code I posted originally was my template. That only fits if you name your fields likewise. This only should demonstrate how that thing works. Your fields are probably named different, so you have to adjust your templates.

Well, it depends on how you configured the image field. If it is set to hold multiple images you get the url of the first image with: $myImageField->eq(0)->url Otherwise, if you set the image object to only allow one image, then you get the url of the image like this: $myImageField->url Either way, this just the url. For outputting the image in the template you have to wrap it in an image tag like so: <img src='{$myImageField->url}' alt=''>

Sorry, my fault. By default the image object returns an array of images, so if you want to have the url of the first image you have to do this: {$image_1->eq(0)->url} // my image field 1 I assume you got this error while there wasn't any template to be rendered or you got an error which prevented the template from being rendered and then caused this follow-up error.

Sorry, I am in a hurry, but two things: {$image_1} // my image field 1 should be {$image_1->url} // my image field 1 Yes, the buttons are always at the bottom (like in PageTable itself). Because of the backend error you got first: I have to take a deeper look. Thx for reporting!

No, just me.

You are right. But instead relying on a canonical I just used a PW solution: if($config->httpHost == "aureliusinvest.com"){ $english = $languages->get("en"); if($page->viewable($english) && $page->url != $page->localUrl($english)){ $session->redirect($page->localUrl($english)); } } Basically: If user accesses the site with the .com domain I check if there is an english version of that site and redirect to that one. Only if the current page isn't already the right one. Since session redirects are 301 by default, Google should index correctly.

Now I understood. You don't want permanent clones, you just want something like an already filled entry. So what you basically want is the ability to clone an existing pagetable entry from a preset. Perhaps take a look at the ProcessPageClone how cloning is done there. But that is beyond my skills to adapt somehting like that to pagetable entries Could be done with a module, which prefills values under certain circumstances on Inputfield::render but... phew.