Mike Rockett

Update: Repo has been moved over to http://github.com/rockettpw/jumplinks and its documentation now lives at http://rockett.pw/jumplinks

Heads up: Per this post, I'm going to be moving the Jumplinks and SimpleForms repos over to their new home on Github. You'll notice there's also a new repo for Jumplinks' documentation - that's because I'm moving it out of the current wiki and into the new site, which will automatically sync with the repo to ensure all is up to date. This will all happen within the next few hours, once I've figured out all the nitty-gritty's.

Hi jmartsch, Unfortunately, I haven't given this much attention of late, but will be getting back into it in January. At the moment, I'm busy moving both modules over to their new homes on Github, and publishing the new documentation site for Jumplinks. Hoping to get the forms module done soon - sorry for the delay.

I think it only works to a certain extent. Modesta hasn't been updated to support many of the new features in the admin panel. That said, the 'base' of the module works.

Jumplinks is designed to remove the index.php from URLs. As such, when you request /index.php, you'll be redirected to the root of the site. Additionally, it's designed to work with redirects like /index.php/MyOldPage.html by swapping out index.php for index.php.pwpj so it can check. If it doesn't do this, then developers wanting to strip index.php out of their old URLs would not be possible. That said, this does appear to be a bug (well, more of an oversight on my part), which I will look into as soon as I get the chance. Requests like the one you've made should remain as-is, so that PW may throw a 404. Thanks for picking that up!

Well, the registry expects everyone to charge respectable/decent/competitive prices - because the price is so low, nobody is really going to argue about it. I paid just over $2 after currency conversion from South African Rands - was charged R31.14. Interestingly, however, renewals are R141.14... Kinda strange.

This doesn't appear to be related to the original thread... Could you please open a new thread for this?

Hehe, totally just claimed rockett.pw. And wow, .pw domains are dirt cheap. Literally. $2.

After several git conflicts (hey, I'm learning), 1.5 has been merged into master - I believe it is stable for production. If you notice any bugs (or other like-minded creatures), please either mention here or submit an issue.

A request to example.php should be caught by Jumplinks if the file or page doesn't exist. My dev installation is doing that. As such, there must be something wrong with your configuration. Jumplinks automatically removes the leading slash. And very glad you like it. Will be updating to 1.5 with a few new features soon.

Nice animation, diogo. Happy holidays to everyone!

Apologies - I came to that conclusion because it is your first post. (Maybe introducing yourself in that post would have helped.) That aside, welcome to the forums.

I think you're a spammer. If you were using ProcessWire, you would know where the configuration file is...

Was desperate to get my surname on South Africa's TLD (co.za), but it's reserved. Unfortunately, the owner won't give it up either, making claims about using it for business in the future. (This claim was made a long time ago, and the domain is still not being used - maybe for email only.) Wouldn't be so keen on the initials method - seems kinda weird. Though, if it has to be done, then it has to be done...

I had the same issue when upgrading to current devns. Landed up doing a manual upgrade, which worked (as expected).

I understand how you feel. It's quite sad that so many people have closed their minds to platforms that either don't live up to their promises, or just fail on their backsides at almost-regulated intervals. Luckily, my experience hasn't been so bad - guess I just have an open-minded client-base. There have been several instances where WordPress was brought up, and an explanation of PW's benefits was required. However, all of these went smoothly, and not one client has forced WordPress into the equation. They're all happy with PW, and have outstanding things to say about it. I prefer to not argue with people, and so would say to a potential client insisting on WordPress that it shouldn't be used just because everybody else is using it, "but, if you insist, here are a few designers and developers that would be happy to help you." (And then proceed to list the 5999 designers and developers here in SA that use it religiously.) It's not easy, I know - but your preference of ProcessWire is exactly that: your preference. And so, it isn't easy to make your clients feel about it the way in which you do. I guess my initial experience was along the lines of my client relying on me and trusting me extensively - to the point where they just ran with it (instantly).

Hi Nico, The theme isn't working with the new front-end editing feature of devns. The only error I can pick up is this: TypeError: $ is not a function in skin.js. Still works in the backend, as expected. Edit: I think this may be due to the way in which you made changes to the loading of the inline editor - around the time it was spanning the width of the page. If I wrap the calls to $ in an anonymous method, the error disappears, but the inline editor does not appear. (function($) { $(".InputfieldCKEditorInline").click(function() { var a = $("#cke_" + $(this).attr("id")); if (a.length) { $(this).parent().after(a) } }) })(jQuery);

As far as I'm concerned, redirects are pretty quick, and so using normal page links in CKEditor along with PagePathHistory should be more than sufficient for managing this. A Textformatter module would also indeed solve the problem, but there isn't one as yet. Also not a fan of ID-based URIs - I just don't see the purpose...

I remember this site, and specifically remember how fast it used to load... I take it you haven't made any other changes? I would assume something has changed on the Media Temple side. This is definitely not a DNS issue - that resolves in about 1.5s here, which is a bit slow, but not slow as the server waiting time of 9.6s.

Yeah, I always rename the admin area. Lately, I've started making it 'siteadministration-', followed by their randomised five-digit account reference tag. So, for example: abcaccounting.co.za/siteadministration-f851z. For ease-of-reference, I ask them to bookmark the URL so they need not remember it. Also building a Client Centre for my clients so that they have access to the URL, should they loose the bookmark. (Client Centre also handles their cPanel email management etc.)

That is indeed intended now. PHP pre-7 simply threw warnings for using control structures outside of loops and switches. This has now been escalated to fatals in 7. @Ryan: I may be wrong, but is that continue even needed? Should it not return false?

Dev branch updated to 1.3.6 adding support for clearing jumplink hits on an individual basis by means of a new checkbox in the jumplink editor. Note that this only clears the counter. The date of the last hit will always be stored. Everything is looking good at this point. Hoping to push to 1.5 stable in about a week or so - please let me know if you've noticed any issues before I do that. Thanks.

It's actually wp-{all} or, to be more specific, wp-<admin|content|login|includes>{all}. The point of my previous post was to make a special wildcard, perhaps called {wordpress} for easy redirection to something funny.

Granted, my solution here is not very polite, but the methodology is there. ;-)

Interesting topic, this. For me, coding is better. Though, there have been a few instances where someone taking over development of a client's site resulted in endless stress because they didn't understand the way I'd put it all together - let's just say I'm not fully standards driven. Luckily, however, a few tweaks here and there often fix the issue, and then people pick up on it pretty quickly. Haven't ever really played with tools like Pinegrow or Macaw before - anyone here have any proper experience to share?