/div errors all over the place

Possible you don’t have one, not a problem for now. Are you able to move the files out of public_html?
You could also copy them to your local drive with transmit if necessary.

Leave the hidden ones there

If your host('s software) is reporting that you’re out of space and were so helpful the other day by moving your files from a previous version back for you, I strongly suggest you put that error (‘Disk Full’) from Transmit to them and ask them to investigate.

It would explain a lot - even though such an error message might not actually mean that literally you have no space anywhere on the part of their shared disk currently allocated to you. It could be that scratch space or some sort of buffer space was somehow unavailable to you into which your ftp operations were expecting to find temporary space. Or that there’s some other source of recursive copying or similar happening. Several sites suggest, admittedly perversely, that Transmit’s Error 160 is actually ‘Permission Denied’, which also explains things.

Please try using Transmit to put everything that Scott and I suggest (minus the hidden files). And then try republishing, monitoring the upload with Transmit to see what happens.

OK, here is what I did. I copied everything in the public_html folder on the web site to a folder on my local hard drive using Transmit. Then, still using Transmit, I deleted EVERYTHING in the public+html folder on the web site. Then I quit Transmist and started up RapidWeaver and told it to republish everything! It would copy a dozen or so file, pause for 20-30 seconds and then copy another small group of files. Took almost an hour but it finally got everything published. Then the moment of truth!. I rebooted my laptop, started up my browser and clicked on the link for the web site and AMAZINGLY, it came up the way I wanted it to… all my updates had taken! While I still think RW has a problem with the web site password process (saving), I found that if I went to settings every time and re-entered the password, it would work. If I did not do that, I got the error that it could not create a folder or something… nothing that told me there was a password problem. my thanks to all of you for your wonderful assistance! Time for bed as I have to get up in a few hours to take my wife to her dialysis! At least I should sleep well tonight! Thanks again!

4 Likes

Duane,

This is great news! Thanks so much for sharing.

Suggest keeping backups, of course.

As for the password issue, suggest exploring exactly what is being kept in the ‘bookmark’ for this site - it may well be that you have to enter the password in that (the book icon in the right of the first screenshot you pasted for us here - above the spanner) and save it one last time.

Best wishes for your wife’s treatment.

You should feel pretty proud of yourself, Duane. Well done!

2 Likes

Well done Duane!
Glad to hear it is sorted once again.

As @MarkSealey suggested keep a backup locally.
I keep the RW project file and the exported site locally.

Not to muddy the water too much but I may have stumbled on the cause of my password problems. I normally don’t use the ‘bookmark’ thing but after it was mentioned I clicked on it and discovered it was holding the password to my ‘personal’ web site. I wonder if when I would publish, RW would ‘assume’ the bookmark entry should be used. Curious. I haven’t touched my personal site in quite a while and don’t recall ever using the bookmark but I must have and just forgot about it. I have now updated the bookmark thing to include the michiganikes site. Will see what happens the next time I do an update. Stay tuned for the next exciting episode!

2 Likes

The bookmark thing was most likely the cause of my problems. Since correcting it, I have successfully published with no errors! Thanks to all of you for your kind assistance to an old codge (grin).

2 Likes