Macrura

that would be a pagetable field.

i would definitely check with the hoster and see if they are blocking bing; i would also follow @cstevensjr advice and try the sitemap;also try and see if you can specifically set the search domain as www version

@noodles - stay tuned - there is a module coming out that handles all page selects, making them configurably link to a modal for the page.There is also some code already here and there and a proof-of-concept module floating around that does this; and Soma also had a module that enabled this function a ways back; will try and find relevant posts later and add here..

just some guesses - 1.) do you have a robots.txt file in the root 2.) have you checked to see if Bing is accessing the same site, www vs non-www?

ok thanks for all your help and info- i will try it again, i didn't know anything about honeypot and that the website field was the honeypot must have somehow missed that in the docs. so can i just change the message input to a textarea, and it should work i guess. i will test and post back results.

probably the best way for what you are asking would be what Ryan did in the CMS Critic Case Study, where you rewrite those URLS for those pages, using a simple hook into the page URL.

@Mike - this is really great, especially the new features; and a lot of care went into the documentation, and is much appreciated.. i hope others will find this useful! will be upgrading that site i was testing on and report back any issues.

@justb3a had some issues; spent about 2 hrs trying to get this to work; some of the documentation does need improvement, for example it should say to echo the module, or the module should echo. for one, there should be a way to disable the whole spam thing, besides putting in the ip address. makes it hard to test; sometimes i'm trying to test this and it's redirecting to the homepage, sometimes the form just shows again with the fields filled in, i have no idea what is wrong; and then i'm trying to do a simple form and change the markup but it either seems to break, or it triggers the spam thing. the message area should be a textarea; seems that changing from input to textarea also was messing things up; i appreciate all of the hard work that went into this, just seems that it could use some additional improvements and some better documentation.. for now i'll have to stick with formbuilder for this site, but have somee friends who need to use this; so we'll have to sort out this textarea thing, and also how to completely disable the spam thing. plus i can fill out a form in way less than 1 minute, so how can that be a real spam prevention technique; doesn't make so much sense; maybe consider some simpler spam prevention like honeypot... thanks for listening.

what are your settings for the submit - does it stay on the same page, or do you redirect to another page? where does your form submit to (action) - self or some other page? main thing when using hanna code for a form is that if you are posting to the self page, the textformatter might somehow cause the form to submit 2x, upon submit

i think the selector redirect is working, wow that's so cool; and i'm seeing the debug log now.

also, i'm still needing to rename the tables in the module to ProcessRedirects, since i'm on unix.. But now it worked, so all of my original redirects are now imported- thanks! will carry on testing the selector redirect now..

hi mike - where should i look for the log, checked the module, and site/assets, but not seeing any logs; also getting this... Mysqli was instantiated and queries were made. These should ideally be converted to PDO ($database). Here are the queries: 0 SELECT * FROM process_jumplinks ORDER BY source [4 rows] [0.0321s, 0.0321s, 0.0365979671478s] 1 SELECT * FROM process_jumplinks_mc ORDER BY collection_name [0 rows] [0.0181s, 0.0502s, 0.136598110199s]

it will only import 1 link at a time from the redirects module; i was able to get 2 of them imported by importing then going to the database, changing the setting to false, importing the next one, etc.. but there must be some problem; also, i can't get the selector to work; i have this entered in the source: store_item_detail.cfm?item_ID={id} and this entered in the destination: [[template=product-legacy,legacy_item_id={id}]] but no luck in terms of it forwarding to the page, just getting 404 and no log with debug on, and the forward doesn't work with debug off;

ok thanks - sorry didn't see those instructions; will be back on this tonight and will report back...

wow amazing.. will test asap. how can i reset things and try the import again - still the issue that my PR import failed...

right - yes it must be a case sensing issue with MySQL. this one i'm running is 5.5.40-36.1-log processRedirects does fail if i rename the table to all lowercase

yeah - sorry - to clarify and answer the above post, i failed to click the last import button, so no problem there; on my 2nd try i renamed the database in the Jumplinks Module wherever it said processredirects i renamed to ProcessRedirects; then i ran the import but it only imported the first one; i can't see how JL queries would have worked because looking at the Redirect module, (unless for some reason i have a legacy version that isn't showing it needs to be updated), it uses $this->className for the queries

ok - i renamed it then ran the import; that seemed to have worked, but then when i renamed it back to ProcessRedirects, Jumplinks doesn't show those anymore ok i didn't actually click the final import button; so i went into the jumplinks module, renamed the tables to ProcessRedirects, and then ran the import but it only took the first redirect; now it won't let me do it over

for some reason the table in my install is upper camel case, so the table is called ProcessRedirects.. i wonder if i should try changing it on another note - is there any functionality to find a page based on a field - for example, i have the legacy IDs stored with the pages themselves, and i was using get vars on a template to redirect to the page; wondering if JL can handle this. so instead of a mapping collection you would have a selector? template=product-legacy, legacy_item_id={id} one last thing - the start and end both say 2015 years ago

i have a site which was using redirects and am migrating those into Jumplinks. when i try to import, i get errors and can't import.. Table 'walsh_prowire26.processredirects' doesn't exist SELECT * FROM processredirects ORDER BY redirect_from#0 [internal function]: Database->query('SELECT * FROM p...') this is an older site but it does show i'm running the latest process redirects module

session redirect also sends 301. my way should work fine

not totally sure (untested) but since /index.php loads the homepage, you might be able to allow get vars on the homepage template and then put in some logic there to process the request... if($input->get->id) { $pid = (int) $input->get->id; if($pid === 33) { $fwd = $pages->get('/products/'); $session->redirect($fwd); } if($pid === 36) { $fwd = $pages->get('/contact/'); $session->redirect($fwd); } if($pid === 37) { $fwd = $pages->get('/imprint/'); $session->redirect($fwd); } }

we would need to see the output, not only the php code - i don't think there is anything in your code that would cause the form to submit twice; it probably has to do with how you are using the hanna code; can you post the html output? this form posts to itself, so somewhere in there some variable is allowing it to process twice. this PHP file also needs to have access to the api since you are using api vars. http://cheatsheet.processwire.com/ so it can't be a file just sitting in the root, in case that's what you are doing - it needs to be a template file; you might want to test this not using a hanna code and see if that works; you could simply make a template for the contact page and then include that file there.

wow that's amazing

@Mike - thanks - that totally works; maybe this info should be in the readme for the lightwire - will post on github ah just noticed Nico's post - @Nico - just added an issue, requesting Mike Anthony's instructions to be in the readme.. thanks for making this, liking it a lot!