Today GW has been slow to load. In fact one thread never did load so had to go back to the list of threads and try a different thread altogether. So far today, the ad has not gone crazy covering the words. Hopefully the powers that be have mastered this problem. Like so many of you, I sense a shift in the people who post here and the GW atmosphere. I've only been around for 1 and 1/2 years, but I agree with Breezy that it seems that many of the long time members who posted a lot when I first found GW are not frequenting the site. This makes me sad. It is selfish on my part, but I had hoped that they would be around to help with my kitchen layout for our reno. They really give valuable insight! I have marveled at their skill and also their generosity of time spent helping others. So Breezy, Rhome, Marcolo, and so many more of you talented people please don't leave GW. Persons like me really need and appreciate your advice. You are Godsends to those of us who are floundering in this remodel maze!

Random placement: I haven't had that problem, but I always make sure my curser is at the bottom of the page when I start to upload a photo. If you've clicked outside the message box, the curser sends the photo (or link) to the top of the message (or where ever the curser is in the message.)

People who need to know a particular tree wants to grow over 60 ft. tall where conditions permit are those wanting to plant the same kind where there is room for one about 15 ft. tall. Something that happens a lot, particularly when many appear to think "big tree" = 15 ft. The physical demonstration of genetic programming recorded by those measuring fully developed examples illustrates the inherent character of trees being considered. Doesn't matter if they don't all grow 100 ft. tall everywhere, when even half that would overwhelm the planting site. Or that it might take 50 years for them to get big. It costs thousands of dollars to hire a qualified tree service to remove one big tree in a developed setting, where it can't just be sawed through at the base and allowed to fall where it may. And left to rot. Why ever choose a tree for an inadequate space, when a smaller kind could have been planted instead? Denial that a particular kind does often loom large does not prevent this problem from developing down the road. Plants that burn - or worse - every time there is a sharp winter may not really qualify as landscape staples. Certainly not as the ironclad, fail-proof unchanging purchases probably nearly all non-hobbyists are visualizing at the time they bring landscape plants home and install them. Hence the value of pointing out specific items aren't, in fact totally hardy - as in never damaged by cold. This is why there are hardiness rating systems and hardiness categories like fully hardy, half hardy and so on - people want to know where each plant falls on the spectrum, what to expect.

If you fire up your old macbook and you're still signed into gardenweb using Firefox, you may be in luck. If you are logged in using Firefox I could do a more step-by- step on how to locate the cookie file. Firefox makes it easy to locate the correct folder. Another way to find troubleshooting info by going through the hamburger menu. (the three lines) Or even better: about:support Then you'll see where to open the profile directory and find the file. I don't like Chrome either but probably for a reason that doesn't matter to most anyone else. (I prefer tabs on bottom, Firefox lets me do that, Chrome does not) The error you posted is the one I get. Other browsers might word it differently but it's the same error. Anyone that does not have trouble with gardenweb(dot)com links, it's because you haven't logged out, either intentionally or inadvertently. Unless Houzz fixes it, sooner or later everyone will be using houzz(dot)com. I like the way gardenweb is styled better than houzz so I'll use it until I can no longer use it. I can picture the techs pulling their hair out and cussing every time they make a change on houzz that breaks something on gardenweb. Anyone that is logged in using gardenweb(dot)com and prefers it over houzz(dot)com, don't log out or clear cookies. :-) "If you can get in on chrome you’re leaps ahead of me!" I missed that. Same here. Maybe in whatever way the OS update messed up Firefox, it just didn't mess up Chrome? Perhaps sitting beside a new Firefox profile is an old Firefox profile with a logged in gardenweb cookie? I might go to the currently active Firefox profile by going through "Troubleshooting information" as above then hit the up arrow and look for another profile directory. Inside that older profile might be a cookies.sqlite file that once pasted into the active directory, would switch you to signed in. (close Firefox before pasting the replacement cookie file, then start it back up) Probably too much to hope for... but worth a look see?