Russell

So, I finally have time to look at my issues. So I get on to check the page load again, and now it works. Try on a different computer at a different location, and it works there as well. Seems it's corrected itself??? Sounds like a DNS issue to me. Why it would take so long to fix itself I don't understand. I'm not sure what else to think? Thanks for the suggestions. I'll consider it "resolved" for now, until something else proves otherwise.

It is actually a different header image on each page, so that's not an issue as such, although I do need to correct it. As for templates, there are a couple of different ones in use. I missed my coding window of opportunity for another day, so I'm on hold till I can get some programming time.

Thanks for the suggestions. No I haven't tried debug mode. I'm stuck at work for the next 8 hours or so. If I get a chance tonight I'll try them out and see what happens.

Yes I went through all if that before posting here, although with the number of permutations in .htaccess, I probably didn't try them all. However that's why I created a test site, to see if the standard .htaccess worked for me. Given the test site comes up fne, doesn't that mean the .htaccess isn't an issue? I also compared the config.php between the two sites, and apart from the database login details, that looks the same too.

I'm still not having any luck here. Are there any cache settings in PW itself I can set? i didn't see anything in the admin screens. Could there possibly be something bad in the database that I copied from my development site?

I agree, and I didn't put it there. I have no idea how it got created. The older version was in the proper location at this local path :-/Applications/MAMP/htdocs/maryvalecommunity.com/site/modules/Blog The newer version was in this local path :- /Applications/MAMP/htdocs/maryvalecommunity.com/site/modules/Blog/Applications/MAMP/htdocs/maryvalecommunity.com/site/modules/Blog It's fixed now I think - my live site is still bugged so not 100% sure if something else screwy has happened, but I don't know how it happened in the first place.

It looks like something went screwy when I tried the update from URL, or somewhere along the line, as I have a second copy of the module installed in a sub-tree of the modules directory, which mirrors my local drive path to the original modules directory. As a result, I think I have some old and some new files in my install location. So, I just want to manually refresh all the core files without doing a reinstall. Should it be OK to simply delete everything under the blog tree, except the templates directory, which I've customised, and put in a fresh copy of the current dev files/folders?

Thanks for testing. I hope this indicates something to someone, as I have no idea how to investigate that further. To move the site from my local machine to my server, I just zipped the whole structure and moved it to the server, as per the move tutorial in the documentation. Could there be some temporary files that went with the archive, that need to be cleaned when moving a site? If so, how do I do that? *EDIT* Browsing around the site files, I did find something odd, but am not sure this should affect anything. Under the /site/Modules folder, there is a Blog folder, but there is also a Applications/MAMP/htdocs/maryvalecommunity.com/site/modules/Blog which seems to be a second copy of the blog module, installed under my local dev site path, below the modules folder. I don't think this branch should be here, and I should be able to delete it with no effect, but maybe if the install is linking down there instead of the top level module, something screwy may happen? But the blog module is not my home page anyway, it's just a standard PW site at that level? *EDIT2* I moved that Applications/ tree away, no difference, so I guess that's not it. *EDIT3* Well I've tried tidying up stray files, removing cache files, and looking for odd files in strange places, all with no change. I'm stumped.

Hi all, Well I finally just moved my first proper Processwire site into live, after developing in MAMP on my iMac using Chrome to dev in. I loaded the site up in Chrome and it works fine, and I've edited some pages and have seen the edits applied when I reloaded the site. However, upon further investigation, when trying Safari on the iMac, iPhone or iPad, it is giving the dreaded "Internal Server Error" message. So I tried running parallels for Windows 8, with IE and Chrome in Windows, and neither of them works either. Why would chrome on iMac work, and nothing else? Is it some sort of Cache issue where my development browser is accessing cached data, and none of the other unused browser have this info? My site has been implemented with PW 2.5.0 & the latest dev version of Kongondo's Blog. Any suggestions where I need to look? The site is http://maryvalecommunity.com if anyone wants a look. Thanks. Russell. *edit* Well this is odd. I setup a default PW install in a sub-directory to the main site. when I test it, it works. Then after testing it, then going back to the above domain, that then works as well?? Can anyone explain this odd behaviour for me? Is it DNS caching? When I first put the main site up, it did have an error because I had mis-spelled my DB-User name. Maybe that version got pushed to DNS and the unused browsers are hitting an old version, or something like that?

Oh sorry I think I've confused you. The module was not updated by the update process. I ran the "update from url" step, but then when I looked today, the module was still the old one. No drana I just downloaded the .zip again and overwrote with the new module. As for aurhor name, I have it displaying my name fine, but the problem is the link url still shows the username, not the display name, thereby giving someone withp malicious intent a foot into the backend door.

Something else I've just come across. Since I'll be probably posting articles and don't particularly want to swap between an admin login and an author login all the time, I was hoping for some way to change the Author links to use the display name, instead of the username. I'm guessing this would require module changing and not just something I could code myself while still using the MarkupBlog author functions?

Hmm, not necessarily a blog issue, but I did the update last week and it all said it worked fine, but I've only just got around to trying the comments change, and when it didn't work, I looked at the MarkupBlog module and there are no changes in it. Not a drama I can change it manually, but I wonder why it didn't work?

Fantastic! Wish all updates were that easy. Thanks.

Thanks for the quick update. I just want to double check the update process. An earlier post in the thread said you can just upload the new module and update it from the admin area. So this won't try and reinstall anything, it will just update the code? Or should i just be copying in the updated module?

Thanks. Yeah I actually started out with the blank templates, but then I realised I didn't know how to access the ProcessBlog data, so I went back and reinstalled with the demo's. My bad I looked for the docs but didn't find them. That should solve all my problems, thanks Russell.