Mike Rockett

I've made few changes, which I'll be uploading tomorrow morning as v0.1.1. Some of it is to do with bettering my code (specifically in the way of Regular Expressions), and the rest of it is to do with better path cleaning, and a few backend CSS fixes.

Have you tried with any other versions?

That may be because you switched these two rules around when you were encountering problems: # ----------------------------------------------------------------------------------------------- # Pass control to ProcessWire if all the above directives allow us to this point. # For regular VirtualHosts (most installs) # ----------------------------------------------------------------------------------------------- # RewriteRule ^(.*)$ index.php?it=$1 [L,QSA] # ----------------------------------------------------------------------------------------------- # 500 NOTE: If using VirtualDocumentRoot: comment out the one above and use this one instead. # ----------------------------------------------------------------------------------------------- RewriteRule ^(.*)$ /index.php?it=$1 [L,QSA] As such, it's looking for index.php in the root of domain, not the root of the installation. If you swap them around again (comment the second one, uncomment the first one), it should work. Please let me know if it doesn't...

@renobird -- Glad you like it! Yeah, please; I'll appreciate that very much.

Ah, right! My brain has been very much turned off... (When I asked the question, I had a scenario in mind - whether or not this impacts it is now lost in the wind. If it hits me again, I'll mention it.)

@netcarver - yeah, will do so. Thanks. Edit: Done

I could certainly write one for my module, but I really think it's something that should be in the core... Wouldn't you think?

You'll need to declare a RewriteBase: RewriteBase /sito/ There are examples from line 118.

(Removed)

Jumplinks for ProcessWire Latest Release: 1.5.63 Composer: rockett/jumplinks ⚠️ NEW MAINTAINER NEEDED: Jumplinks is in need of a new maintainer, as I’m simply unable to commit to continued development. Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa. The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them. Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation. As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run. Documentation View on GitLab Download via the Modules Directory Read the docs Features The most prominent features include: Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy: Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Open Source Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.

Me being dumb again -- 'updated_at' is not a string. Very clever indeed. Edit: No, that wasn't it. But it works now...

As the title says... I'm using the following config: $options = array( 'items' => $redirects, 'itemLabel' => 'name', 'itemLabel2' => 'updated_at', 'edit' =>'entity/?id={id}', 'add' =>'entity/', 'addLabel' => 'New Redirect', 'sort' => false, ); Using 2.5.12 (haven't updated to 2.5.13 yet).

Ah, my bad... I'm quick to click! Thanks

I have seen this, but it's specific to message. I need it for processing decisions.

That looks pretty decent indeed. Thanks

I think it would be really nice to have $session->flash('key', 'val'), only valid for the next request. What do you think? (I know I need it...)

So I've been wondering... What happens if a module gets an upgrade and it's DB table(s) need a schema update? Any decent way of handling this?

(removed)

Turns out #MyTabs needs to be a form. Then it works. Seems hacky - I don't need a form...

@Pete - I'm using your method with my new module, but it's applying padding when using the default admin theme: If I remove the margin from #MyTabs > .InputfieldContent, the result is: Am I doing it wrong? Reno theme works perfectly. As does Apertus. Modesta doesn't, but I'm not worried about that.

Tom: Regarding Legacy Domains, do you think it may come in handy if we were to add per-redirect exceptions? Perhaps you want to keep a URL on your legacy domain, but if its accessed on the new site, you don't want to redirect to legacy. Yes?

It's evidently the last bits where you're redirecting to http404, which I don't think is the greatest idea. Perhaps you could just output a message if the segment isn't specified?

I find it weird that you're being redirected to /http404/ - it's supposed to pass-through that URL, and display the URl that was entered (/drains-backing-up-total-drain/) in the address bar. So that's your problem there - perhaps another module is interfering, and forcing the http404 redirect? What have you got installed?

Module should be working fine... Are you getting an Apache 404, or a ProcessWire 404? If it's the PW 404, please could you send a screenshot of your redirect's edit page or a dump of the redirect directly from phpMyAdmin?

(Removed)