Mike Rockett

Dev branch bumped to 1.3.5 with an important fix. compileDestinationUrl was not returning the correct data, which resulted in relative redirects. This issue has now been resolved, and the behaviour is the same as the current stable. Looking to push to 1.5 soon for stable release - please test... Thanks!

Great, thanks Adrian. Yeah, just the two modules (for now...)

Hey Adrian - yes, please. I guess they should all be merged into the third one, which equates to the named version of my profile display name. Or, even better, they should actually be merged to my GitHub username, which is the last one. That possible? Thanks. (Oh, and I'm not sure about the first one - I may have tried to change my display name to just mike at one point, but didn't think it would affect the modules directory...)

Hi kixe: replied here: https://processwire.com/talk/topic/8697-jumplinks/#entry107615

Hi kixe, Hehe, glad you found it. I would like to have an option to clear the 'HITS'. > I will be adding that option to v1.5. It isn't listet if I select modules by Modulauthor mikerockett mikerockett or mike-rockett (better to merge) > Thanks for picking that up - not sure why that happened. Hoping an admin can pop in and assist with that...

I don't think your question is very clear - you'll probably need to clarify it if you need assistance.

Hi Mediamar, I'm sure you've already begun digging into the documentation, but you can use the following redirect to match all URIs using a php extension: Source: {path}.php Destination: {path}/ Glad you like the module.

Votes are in, and nearly unanimous: The module will be renamed to RockettForms when I get back into it. (Unable to commit enough time at the moment, but will get there.) Also, I plan to make this a 2.7-only module. If you think I should drop that to 2.6.1, let me know.

Looks pretty cool indeed. And glad you're using Jumplinks. I think the only suggestion I have at the moment is to improve the UI controls. At the moment, the select boxes are native, so they kinda look out of place due to the darkness of the site. Perhaps using a dark Chosen or Select2 skin would help on that front. I'm also sure it's possible to make the Facebook comments plugin dark. Not sure though - only ever did it with the old version.

Just as a follow-up on this: In a private discussion with Jeff last month, I noted that this scenario will be accomodated in the next version. However, if there are more Jumplinks users bumping into this issue, then I would want to make it part of 1.5. In the discussion, I mentioned there would either be a checkbox in the entity editor that allows you to make query strings optional, or that we could use square parenthises to mark them as optional, like this: bioh[?gclid={token:any}]. After a little thought on the matter, I think it may be better to use the checkbox approach for query strings. However, I think the behaviour should be somewhat different in that it would let you choose to "ignore the query string in source" and, if that is selected, "append original query string to destination". Thoughts? In light of the square parenthises idea, I also have plans to make parameters optional, like so: {?title}

^ The one thing that turned me away from MODx the minute I saw it. Phew!

Hi, and welcome to the forums! The ProcessWire eco-system is active. Ryan Cramer, the creator, is continuously adding new features to PW (on the dev branch) and fixing bugs as he goes along. The community here is small, but active and very helpful. The Modules Directory is also active, with some interesting modules popping up on a regular basis. As mentioned above, PW3 will be Composer-ready, with namespace support. Many here are quite excited about PW3. Version 2.7 is just around the corner (maybe this week), and contains several great updates in comparison to the current 2.6.1 stable. So yes, I recommend the jump.

My apologies - I hadn't even read your full post before recommending it. ;-)

Might be better to use Protected Mode: http://modules.processwire.com/modules/protected-mode/

You could make use of Jumplinks - 302 redirects are used when you set Timed Activation.

Excellent stuff! Shall be giving this a shot soon. Thanks for the module! (Heads-up: the GH link takes me to wanze's TemplateEngineTwig...)

I doubt that will help, though. The browser automatically sends requests in full-URL format...

That wouldn't help as the same error happens in cPanel.

With strange URIs like that, I could only imagine that the account was hacked somehow... As your templates are okay, my only guess is that this could be htaccess-related.

You're very welcome indeed.

Question: any particular reason why the form needs to be processed outside of PW?

Quite nice indeed, though I have a few suggestions/recommendations: Fonts are inconsistent. Some areas use Open Sans, others use Droid (which defaults to serif and has no @font-face). (Though, at a second glance, I see that there are references to "Droid, serif" where it should be "Droid Serif, serif" - I take it "Droid" is not a font, which is why its defaulting back to serif (in my case, Times New Roman, which is a terrible font)). The shadow under the main menu (nav bar and drop-down) is at a 45-degree angle, leaving an area of whitespace to the left of the shadow - doesn't look natural. I recommend changing that shadow to: box-shadow: 2px 0px 14px rgba(0,0,0,0.2) The submit button in the footer needs extra styling - specifically, a border is needed there. The two rows of white blocks with the learn more buttons should have a transparent border applied. Why? Because when you hover over them, a new border is applied, and the text moves down. Applying a transparent or white border should resolve that. I think that the search box could do with some more work... It's quite small, and doesn't seem to fit nicely in the navigation/header bar. On content pages, I think the breadcrumbs bar could do with a light grey background. The sitemap list could do with some styling - perhaps some custom bullets or block elements would help on that front. That's all I can think of at the moment. Well, that's all that is prominent to me at the moment. Otherwise, nice site, and congrats on the release. Quick tip: Your post content is in a code block, which means I have to scroll left and right to read the content...

John, welcome to ProcessWire, and to the forums. As said already, great intro. I find it fascinating that you've gone from one end of the spectrum to the other. You just don't see that often. That said, with your confidence (and seemingly good general knowledge regarding this end of the spectrum), you'll do just fine. And, of course, we'll all be willing to help you whenever you need it. So welcome, and enjoy the ride. (Hmm, so I'm busy thinking about this electric sign for PW - imagination running wild... )

Added two 'likes'.