Mike Rockett

@chrisbourn - what happens when you navigate to /gallery.html? Feel free to PM me your entire htaccess file and I'll be happy to help.

Given that the module hasn't been updated in six years, I'd imagine there's a bug or three (though I haven't tested)..

Quick questions: Should the module - ping sitemap engines (after cache-revocation)? add /sitemap.xml to /robots.text if it exists and is not already added? (This would be done at install-time, and removed at uninstall-time.) For anyone who may be curious about it, I don't plan on adding XSLT support. End of the day: sitemap.xml is intended for the viewsing of search engines, and not humans. If you want a visual sitemap, best to create your own.

I'm making progress with all the necessary changes. On my dev server (not git-pushed yet), the following is complete: Languages: Multi-language is sorted. It now renders the sitemap according to Google standards, where a page's <url> is generated for each languages with alternate langs, including current. Method is not the same as above example (page-loop), but expands on the root-first-then-children process - this allows easier flexibility in terms of what we can ignore on a page by page basis. ISOs: Haven't created the separate language ISO field yet, as my my main concern is regarding names vs ISOs. If they are normally identical, then we would only need to declare a proper ISO name for the default language only when its URL matches the default root URL (ie: default URL root = site root). In this case, perhaps it would be better to simply have a module config entry for the default language only? The rationale behind this is that the language name (other than default) should be the same as the iso (for better SEO practice, I'd guess). I haven't yet bumped into a ProcessWire site that doesn't use the ISO for each language name accordingly. If I'm wrong, please point it out, and then I'll use the iso field, per the above example. Or perhaps I should simple allow the flexibility and have the ISO name fall back to the language name if not provided via a field (the default would still need one if it is root)? Image-support: Images are now picked up in all languages, given the process-change. If an image field is not specified in another language, it will fall back to the default language. Support for ImageExtra remains. Priority: not done yet. I'll follow a basic principal with this: if the priority is set on a specific page, then it will be added. Otherwise, the tag will be left out. If this is not the correct methodology, please let me know. (cc @psy) Note: I still need to do some testing on this...

@chrisbourn - Redirect and RewriteCond/Rule are not part of the same module, and so that line is invalid because of the flags at the end. Rather use the following underneath RewriteEngine On: RewriteRule ^gallery.html$ /new-gallery.html [END,R=302] When you're happy with the redirect and you wish to make it permanent, change 302 to 301.

Okay, so it turns out I was wrong, but only for the bottom, which kinda makes sense for them, but may not work nicely in a range of scenarios. Edit: landscape mode crops both sides.

If the guidelines are anything to go by, the safe area would be the absolute maximum size that Safari would display a site.

In all honesty, I much prefer the Galaxies. Apple boasts by calling it a bezel-less display, or something like that, but they’re exaggerating, truthfully. End of the day: If you were to add the bezels at the top and bottom again, the sides would look terrible. The housing at the top drives me nuts. The MiMix2 is better in terms of the ‘infinity display’ era of phones, alongside the S8 and Note 8. I really like those concepts. Apple is not what it used to be. It’s starting to get all funky and ‘cool’, and the classiness is not what it once was... Re: websites being cut off: I don’t think that’ll happen... The browser chrome will fill those spaces. Also in agreement re: the dock. That thing is fugly. 'Scuse my French.

@psy - That's on my wishlist too ;-) Yes, I'll definitely implement this.

Ah, I see. Doesn't do that for me. Well, it does the first time, but quickly disappears and then I have to click on it to open it.

I see it now automatically merges replies. That's pretty cool. (Except this one, because it has no quote...)

Interesting... Still not for me. One click to open the reactions bar (unlike Facebook's hover) and then another click to Like (as in, select from the reactions bar). They do appear to be shown initially for me.

Hey Pete, thanks for doing the upgrade. I guess not much has changed from an appearance point-of-view. My only gripe is the reactions bar - I now I have to click Like twice, and the chances of me using other reactions is very slim (this isn't a social network, after all). Any chance it can be disabled? Unless anyone has any objections... Also, this issue is still present (really long initial tag): Thanks!

@PWaddict - Thanks! I totally missed out on the actual requirements there. Will work on fixes based on your code soon. Note sure why some of those pages are being ignored as I didn't experience that myself... Will look into it. @maxf5 - After fixes, the module will create a language ISO field and automatically add it to the language template.

@maxf5 - Glad you like it, and thanks for the post. I still need to work better multi-language support. Even at this point on the multi-lang site profile that PW ships with, the first alternate is identifcal to the main URL in terms of what they contain. Yours is a little different, and so I'd need to envisage the possibilities before working on it properly.

If the two domains point to the same server and document root, then you should probably just do a wildcard redirect. Or, even better, make it redirect if the non-IDN is not being accessed (seeing as it's the only domain in your hosts array): RewriteCond %{HTTP_HOST} !muehldorf\.de$ [NC] RewriteRule ^ http://muehldorf.de%{REQUEST_URI} [R=302,L] I'd recommend that you make this one of the first condition/rule sets, just under RewriteEngine On.

Best not to use the Redirect directive. Rather use RewriteRule ^page-one/?$ /page-two/ [R=301,L] just after RewriteEngine On. Alternatively, use Jumplinks.

Jumplinks is compatible with v3 (though not thoroughly tested). As for multi-language, it is not specifically supported in terms of the additional features. However, a 404 event would still trigger the jumplinks routine. Please enable debug mode in Jumplinks' config and paste that log here. If it's very long, please add as an attachment.

The issue is that the script won't be imported if only text fields in a repeater are using a slider. The field is not rendered until AJAX-time, and so the script cannot be imported. I'd recommend that you simply load the assets at page-edit time (separate hook). Alternatively, and this is just an untested theory because I need to rush out, maybe you should rather hook to the page edit event instead of the text render event. You could then check for all fields (repeaters too) on the page to see if they need a range slider, and then import the assets. That way, all fields are considered, and the event-fired will bubble from the repeater, thus setting the slider.

Hi, It is discussed somewhere in this thread. The problem is that a request like that is a request to the home page, and so the 404 event will not be triggered, and so Jumplinks cannot intervene and do the redirect. You will need to use .htaccess to redirect all of those requests to something that Jumplinks can handle. Unfortunately, this will result in two redirects every time, but it's something you would need to work with in order to use Jumplinks. In your .htaccess file, add the following on line 99 (just below AddDefaultCharset): RewriteCond %{QUERY_STRING} ^main=(.+)$ [NC] RewriteRule ^$ /rq [R=302] When you request example.com/?main=something, it will be redirected to example.com/rq?main=something, and then you can create a jumplink for it.

Ah, of course. Url segments is something that can't be supported because of how they're created... No easy way to keep track of them.

Laragon allows for multiple virtual hosts so that you need not change your document root. If you do change it to your project's working directory, then it would be served via localhost. As such, the localhost domain should point to the default Laragon www directory, and any virtual hosts you define via the Quick Create method will create a new directory inside the localhost document root, and the virtual host will point to that new directory. So the setup looks something like this: localhost -> path\to\laragon\www (navigating to localhost should show a listing of your vhosts, just to test that it's working) - angie.local -> path\to\laragon\www\angie\ - test.something.local -> path\to\laragon\www\test.something\ - laravel.local -> path\to\laragon\www\laravel\public\ - (etc.) In my case, I have a separate drive just for my sites, and so my document root points to z:\sites. I'd suggest you do is open up the Laragon context menu and select Quick Create -> Configuration. Add the following to the file that opens in Notepad++: ProcessWire=https://github.com/processwire/processwire/archive/master.zip Then, when you go to the Quick Create menu again, you will see ProcessWire listed. Select it, and it will ask you for the name of the project, so just type in the name excluding the domain extension (TLD). It will automatically create the new virtual host that points to the subdirectory in your document root, and your hosts file will be amended automatically. In the case of ProcessWire, the virtual host that Laragon creates will automatically point to the subdirectory as its document root. If you Quick Create Laravel, however, it will point to the sub directory's public directory (as shown above). This is a little 'smart' feature that Laragon has to make peoples lives easier. Hope that clarifies everything for you.

I can't make sense of that at all -- there's no reason I can think of that it'd be happening. All basic requests to the directory are supposed to be passed through index.php?it={req}, and so if it's not hitting index.php at all (hence the error you're getting), then it can only mean that something is interfering somehow... That's the best guess I have, I'm afraid.

Hmmm, I'm a bit confuzzled here. Do all other front-pages work okay?

You're welcome. Are you actually redirected to your home page, or does it not redirect but does show the home page?