mjd1953

The site is in development on a local machine. It’s on the web as well, but behind an Under Construction plugin. I’ve made an annotated screen grab available here: Archive Page issue

Hope this will suffice…

Grrr… gotta get some sleep. Thanks guys, for holding this blindman’s hand on this. All’s well now.

Well, of course… [smh] OK, so I tried the obvious (which wasn’t so obvious to me, obviously), and confirmed, AIOWS is not logging any 404s. Not that it’s a huge deal, but something’s not right. Any suggestions on where to look? The “other plugin” I mentioned in a previous post was actually not a problem, so I don’t think it’s a conflict issue. I was unable to upload a 30Mb video clip and discovered the setting in AOIWS that limits uploads to 10Mb–but only after I deactivated AOIWS, which is what apparently led to this current issue. As I said, not a huge deal, I guess, but when one thing isn’t working the way you think it should be, then you spend a lot of time wondering what else might not be working as it should…

I have now… And I think my questions are answered. Very nice plugin indeed. And excellent support. Thank you!

I may have stumbled on the problem (newbie here)… I am the admin of the site and sent a test post (Draft status) and it posted. I switched to a junk email account I have that WP doesn’t know about and sent a test post and it worked just as I hoped it would.

So… I’m obviously not 100% clear on the interaction between Postie and admin-level accounts, or about the field where you input email addresses it’s OK to receive mail from. Can you point me to a detailed discussion of how all that works? As I said, this is exactly what I needed, and a couple of the add-ons look very promising as well. I just need to be sure I understand exactly how Postie decides what to post and what not to post.

Thanks for the quick reply, by the way!

Ahhh… changed the name again, huh? Very clever. If it had been a snake… well, you know… Thanks for the assistance!

Well, it’s kind of embarrassing, but on the chance it might help others, here’s what happened.

As I said originally, I was able to determine that the problem was with .htaccess after using WP Crontrol and finding that access to that file was a problem. I had already downloaded and scanned the (very large) server error log from my hosting provider, and as I looked through .htaccess, I recognized one of the ip addresses (blocked, with wildcards in the last three octets) as an address I’d seen in the error log. I did an ip lookup on it and discovered that it was owned by my hosting provider… I’d had a problem with somebody from 37.146.-.- and inadvertently blocked the whole range by using 37.*.*.*. Well, sure enough, my hosting provider happened to be in that range… I tweaked the Deny froms to reflect this, and problem solved. Sorry if I bothered anyone with this…

Ne’er mind. This experience lasted about a half-hour, then mysteriously went away. All other pages on the site loaded within a second or two, but the one with the Store Locator on it consistently took more than a minute to load. After a half-hour or so of trying, all the sudden it started loading as expected. Obviously something external to our site (since all other pages were unaffected) and to your plugin (it never threw an error), but I haven’t a clue what it could have been. Just glad it resolved itself! Thanks.

Yes. 3.91.1 fixes the problem. Thank you for your diligence in getting this addressed!

Sorry… too fast on the submit… No I do not know if it alters the priority of functions hooking into the “wp_head”, but as I said previously, I do know that reverting to 3.87 fixes the problem…

Discovered that if I revert to 3.87, it works fine, so it seems to be something about 3.91…

I took the page out of cut of circulation, but you can still reach it here

Wow… Probably should have mentioned that I’m pretty green when it comes to php. I think I get most of what the suggested link says, but am not sure still about where to put the custom feed so that it’s not overwritten by some future version of WordPress.

Yes, I’ve got it working now. The fix alone didn’t do it (1.0.1), but when I “Saved” the widget setting, everything was back to normal. Thanks!