Macrura

hey thanks a ton for looking at that, i will continue testing later today and this week and see what's going on.

@Mike - i'm wondering if there is any chance that this module may be conflicting with page path history? I have page path history enabled, and also page path history manager; I see the URLs that PPH should be redirecting to, but they no longer work; I haven't uninstalled Jumplinks to test this because i'm fearful of losing my existing Jumplinks (much to my horror, when i uninstalled the Redirects Module for testing, it deleted all of my redirects; fortunately this was after i already imported them to JL)...

amazing site, absolutely stunning!

yeah, ran into this issue recently and was banging my head against a wall until i realized my items needed a template, because the rss feed needs a link for the items; in my case, the template for the RSS item does a simple redirect to it's parent page with a hash to the id of the item (it is an event listing). if you don't have a template for the RSS item, how would people click on the link to your item?

wow this looks great! I have several sites that could use a good calendar management interface, and i've also been gradually designing my own version of a php calendar in PW, based on the old Thyme calendar.. this will surely give me a boost.

@CliffG - i've never had to do steps 5 or 6. Most if not all PW references in the database should be relative to the root; the only thing that typically needs to be updated when moving a site would be a path that is stored by a module, for example admin custom pages stores the server path to the file it renders for the custom page, and those need to be reset when moving sites; in CSS, there shouldn't be any URLs that would break when moving a site, they should be all relative to the templates folder. you can also possibly avoid some of steps 5/6 by using vars which could be set in an _init.php, using a css.php for special rules that need to be generated on the fly, though i usually do those in the head since it's not that much.

@Mike - also in terms of the nginx comment, if you run cloudflare, then wappalyzer shows Nginx (and also cloudflare)..

my issues appear to be solved.. thanks Mike! looking forward to using this a lot now!!

I meant that the columns in the PW admin are blank; i didn't check the dates in the database, for the particular site that works...

yes, linux/apache - mySQL 5.5.40-36.1-log - PHP 5.4.3 also, i have another site on the same server and on that one everything works fine; no dates are show in the columns, they are empty. on the problem site which is using the dev version of the module (latest, downloaded today) these were all imported from ProcessRedirects, but then some were added after that and all of the rows show the 2015 years ago;

hi Mike - here is how the date is formatted: 0000-00-00 00:00:00

Hi Mike, all of my jumplinks have: 2015 years ago in the start AND end column; but the fields are all empty, no timed activation. None of the jumplinks work, even though in debug mode it shows Match found! We'll do the following redirect (302, temporary) when Debug Mode has been turned off: - From URL: http://www.ohmspeaker.com/1/Bookshelf-Speakers.html - To URL: http://www.ohmspeaker.com/speakers/walsh-bookshelf/ - Timed: From Wed, 30 Nov -001 00:00:00 -0500 to Wed, 30 Nov -001 00:00:00 -0500 if i go in and set a start and end date for the jumplink, it does work! but i guess this needs to be fixed?

your first sentence is arguable. For years we have all used page fields for selects, radios, group checkboxes. it's part of what you need to do, and once you know how to do it fast and easy, then you just do it and don't get caught up in that sort of "too much for simple case" mindset; it just works. nevertheless, Ryan introduced the options fieldtype for when you want to avoid the page field: http://lmgtfy.com/?q=processwire+fieldtype+options the first 3 results should explain it all.

What Adrian said is right and this Q has been asked a lot of times. You need to first create a field, not of type checkbox. you need to use options field or page field. then you will be able to select checkboxes as the input field to select those options or pages.

sometimes clients need landing pages for marketing/seo that need to live off the root. all of these pages would make a mess in the page tree, so they are stored under /landing-pages/ I always do a hook (as was demonstrated in the CMS Critic Case Study) wire()->addHookBefore('Page::path', function($event) { $page = $event->object; if($page->template == 'landing-page') { // ensure that pages with template 'landing-page' live off the root $event->replace = true; $event->return = "/$page->name/"; } }); on the landing page template: // if someone tries to access this page at it's real location in the page tree, redirect to the fake URL: if(!$input->urlSegment1) { $session->redirect($page->url); } i should also add that on the homepage there is this: /** * First, check to see if there is a URL segment off the homepage * this is used to generate custom landing pages, for marketing etc.. * with a shorter URL, living off the root. * */ if(strlen($input->urlSegment2)) { // we only accept 1 URL segment here, so 404 if there are any more throw new Wire404Exception(); } else if(strlen($input->urlSegment1)) { // render the landing page named in urlSegment1 $name = $sanitizer->pageName($input->urlSegment1); $landingPage = $pages->get(2281)->child("name=$name, include=hidden"); if($landingPage->id) echo $landingPage->render(); else throw new Wire404Exception(); } else { // do the normal homepage... so that's why the segment check on the landing page template, because when it is being rendered from the homepage, if(!$input->urlSegment1) will be true

I use AIOM+ and then regular php to manage the array before the AIOM+ is called.. im usually setting the scripts array in the init, like $minifyCSS = true; $minifyJS = true; $stylesheets = array( 'assets/bootstrap/css/bootstrap.min.css', 'assets/css/font-awesome.min.css', 'assets/css/style.css', 'assets/css/custom.css', ); $jsfiles = array( 'assets/js/jquery-2.1.3.min.js', 'assets/js/imagesloaded.pkgd.js', 'assets/js/custom.js', ); in templates i sometimes do this (if styles/scripts need to be before last one, e.g. if last style is custom/override) $jsOffset = -1; $cssOffset = -1; //1.) Event Calendar array_splice($jsfiles, $jsOffset, 0, 'plugins/eventCalendar/js/jquery.event.calendar.js'); array_splice($jsfiles, $jsOffset, 0, 'plugins/eventCalendar/js/languages/jquery.event.calendar.en.js'); array_splice($stylesheets, $cssOffset, 0, 'plugins/eventCalendar/css/jquery.event.calendar.css'); or simple: $jsfiles[] = 'plugins/soundManager/js/soundmanager2-nodebug-jsmin.js'; $jsfiles[] = 'plugins/soundManager/page-player/script/page-player.js'; $stylesheets[] = 'plugins/soundManager/page-player/css/page-player.css'; then outputting: if($minifyCSS == true) { echo "\t" . '<link rel="stylesheet" type="text/css" href="' . AllInOneMinify::CSS($stylesheets) . '" />' . "\n"; } else { foreach($stylesheets as $stylesheet) { echo "\t<link href='{$templates}{$stylesheet}' rel='stylesheet'>\n"; } } // END IF MINIFY this lets you toggle AIOM and good for development and troubleshooting stuff.. i should also clarify that for brevity, i setup a lot of aliases in the init, like: $templates = $config->urls->templates;

i would say maybe try disabling the upgrades and/or upgrade check module, then also check with the host and see if they have any security rules that your ip is triggering?

that's a good question, i'm not sure, but maybe as a quick fix you could use some jQuery (e.g. using admin custom files) to parse that into formatted html

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.