Mike Rockett

Are you using the Redirects module, or Jumplinks? If you're using Jumplinks, then you can redirect multiple pages if they follow a common format. What URLs are we looking at here? And where do you want to send them?

Hi gdl-joe, and welcome to ProcessWire. That's where the problem lies. You need to add that line just after RewriteEngine On.

Yeah, I bumped into that when developing Jumplinks - had to do an insensitive check. If I'm not mistaken, it depends on which version of MySQL you're running...

@Teppo - Yeah, it appears that this is indeed a priority issue. I wonder if I shouldn't push it back a bit? It's currently set to 10, and uses addHookBefore. I can't exactly remember why I used an early event here - but when the two modules are separated, things will be different. Out of curiosity, how would I check to see if that output has been modified? Regarding a timeline on these - I don't have one as yet. Currently spending most of my time starting up a special project. As it stands right now, JL is working as expected, and so should be good enough for a while. On most of my sites, I'm leaving the 404 monitor off due the heavy amount of false-positives showing up.

Indeed - it is fine to leave the tag out of the destination. It must be used in the source as Jumplinks checks the request from beginning to end.

You can just use articles.html?tags={tags:all} and then use {tags} in the destination. Had a look at the docs for wildcards?

Thanks for identifying that, which is indeed a bug - not sure when it broke. Will check it out now. Edit: Fixed - please update to 1.3.2.

Welcome aboard, Rick. Looking forward to seeing the work you come up with.

With these, it's best to tackle them one by one. For this particular one, place the following directly beneath RewriteEngine On: RewriteCond %{QUERY_STRING} ^sa=[^&]+&ved=[^&]$ [NC] RewriteRule ^(.*)$ /$1? [R=302,L] This will trim out the query string and revert to /name-of-page.

Very nice module - I quite like the idea, and it looks to be very well implemented. Kudos!

@Ivan - Hmm, seems strange. Could be a 301 cache issue? Generally better to work with 302 until you're sure it's working correctly. If that's not the case, I'll clone your setup here and see what happens.

A better approach would be to do this: RewriteCond %{HTTP_HOST} ^example\.com RewriteRule ^ http://www.%{HTTP_HOST}%{REQUEST_URI} [R=301,L] So, only force the prefix if we're accessing http://example.com/.

Interesting indeed. I believe that CKE skins do not depend on one another. A port is simply a copied version of the skin with modifications. Not entirely sure why minimalist isn't working as the code looks to be correct.

I used the same syntax as shown above. So far as I know, nothing else needs attention - it should just work as expected.

I did it like that for the Office skin - it worked like a charm for me. Haven't tried with any others, but I think they'd be plug 'n play.

Always been a fan of mod_rewrite, and so I never use Redirect or RedirectMatch. You'll be better off doing a simple RewriteRule just below RewriteEngine On. RewriteRule ^old.html$ /new-location/ [END,R=301]

https://processwire.com/talk/topic/10336-lightwire-skin-for-ckeditor/?p=98429 It's just a matter of specifying it in the global config.

Is this for a ProcessWire installation? If so, use the Redirects or Jumplinks modules.

It's disabled by default anyway - it is doing what it's supposed to do. Only enable it if you want it.

You're welcome. It isn't on GitHub - I don't really have plans to make many changes. If I land up expanding on it, I'll push it to GH. Too true - I shall no longer reduce the lifespan of your mouse.

Also true. Thanks.

How about: <?php if ($page->blog_category) { echo "Posted under: " . $page->blog_category->each(function ($index, $cat) { return "<a href=\"{$cat->url}\">{$cat->title}</a>"; }); } Needs PW 2.5.27+

A client recently asked me to make a simple utility that they could use to upload files for public downloads. One of the requirements, for some reason or the other, was clean URIs. Thought it best to do it with PW. Too much of a mission anywhere else, really. Called it Dispo, which comes from Content-Disposition. Sharing in case anyone else may find it useful. This is generally for use on a subdomain - client wants it installed at files.example.com. In config.php, there are two options to set: one for the domain of the main website (Dispo will redirect there when the home page or 404 is hit), and the other for the name the company or, whatever. Best to set these as they default to localhost and ABC & Co., respectively. Create files using the downloader template, specifying a title for the file (this, along with the company name as set in config.php, will be used for the downloaded file name). When the entry (Page) is requested, its file will be downloaded. To view the file instead (if the browser is capable of it), add ?view to the URL. Download below: site-dispo.zip

The touch-scroll issue is still there. But I don't think that's a huge issue. Scroll-speed is perfect now, at least for me.

It's better, but I think 20-25 will feel more natural. Scrolling by touch is quite irritating on my Windows tablet and laptop on Chrome in that it doesn't slowly decellerate upon let-go. I wonder if you shouldn't upgrade to the newer jScrollPane... Their demo page (using 2.0.22) works as anticipated.