An Update on Posting Errors

I want to thank you all for your feedback about having trouble posting to the site and assure you that the CR4 team is aware of the problem. It impacts all of us, too. I encounter this problem frequently as I set up blog posts. If you aren't aware of the error that sometimes happens when posting, feel free to read a prior blog post, a log of when the problem was encountered by users, and a recent reminder of user frustrations.

Please do not think that you're being ignored. I have brought the problem to the attention of those in charge of the hardware and software behind CR4. Some possible causes of the glitch were resolved and others are still under review.

So why is it taking so long to fix this? CR4 has always been something of a side or pet project. There are no full time resources dedicated to the site. Moderators and bloggers volunteer their time around their regular work. Programmers and IT folks have to devote time to other responsibilities first. Since GlobalSpec was acquired by IHS, all of our workloads have increased. We've had opportunities to work on new projects that are important to our new company.

CR4 is not less important than it was a few years ago. In fact, IHS is really excited about community. I think that once some of our biggest initiatives get going, community will get some attention, and CR4 might have some opportunities for improvement!

Until that time, I again thank you for your patience. I also want to thank everyone who shares the posting workarounds with frustrated users. We can keep going with our own little engineering hacks! The determination of the posters to this site shows just how strong the CR4 community is and how much everyone wants to be here.

Please continue to log errors on this page. I regularly share it with software and IT folks.