Forum Replies Created
-
AuthorPosts
-
HelenaBParticipant
Another vote for keeping the old forum.
Maybe make people tick a checkbox as they access it to confirm that they understand content there is to do with the "old" version of Genesis and that they need to check their version first.
Finding solutions to issues was much quicker on the old forum's structured sub-fora. It's very hit and miss now - depending on how you word a problem. I do find solutions - but it takes a lot longer.
Studiopress is very complicated unless you are very technical
I've been writing my own WordPress themes for years and I'm often confused by Genesis.
I have well over a dozen client sites that use the current version of Genesis and will continue to do so until I find a way of making the new version as accessible as the old and ensure that it all works reasonably in older browsers. So I will still need answers to "old" problems.
I do hope that if we are forced to contact Support with issues that used to be resolved on the old forum we won't get the "I'm sorry but your query is beyond the scope of support" etc.
Here's a thought for you Studiopress. Stick the old forum on a sub-directory behind a pay-screen and charge a small annual amount (and I do mean really small - $5 or $10) to access it. Think of all the support staff time it'd save you!
HelenaBParticipantThanks Anita - I received the same response.
Which is all very well and lovely except for those of us creating sites for "the public" a quarter of whom are still using IE8. Many of them are still using IE7!
I'm a big fan of fall-back positions and graceful degradation as far as coding goes.
Spent quite a few hours hacking at the CSS to create some targeted IE8 and under rules (really don't like doing that). Not pretty, not valid but at least it works (for now).
Not sure that it would have been the end of the world if they'd created a conditional <= IE8 stylesheet.
HelenaBParticipantIt would be really helpful if Studiopress listed browser compatibility along with all the other theme details.
I have many clients still using IE7 (most can't switch - local authorities for example) never mind IE8. Much as I dislike it, you can't ignore IE8 and themes should tested in modern browsers before they're released.
I find that I can usually tweak Genesis sites to work in IE7 to an acceptable standard as I know they say they don't support it. But IE8 is another matter.
Anita - did you solve the issue on your client's site?
HelenaBParticipantThe error's there in all the ones I've checked - Firefox, Chrome and IE.
Even with the error keyboard navigation works in Chrome and IE but fails in Firefox.
HelenaBParticipantI've got a screenshot of what it looks like. I'll send it over.
edit: Anitac - your email address isn't visible on your site currently.
HelenaBParticipantHi essaysnark.
Yep - recurred early hours of Monday morning. I think it was exactly a week later (which leads me to believe it was something scheduled that caused the problem - just can't pin down anything due at that time).
Luckily I went to that site first thing so I don't think it was noticed by anyone else (the client hasn't been in touch...), Not how I like to start my Monday mornings though. Frankly since the majority of my clients' sites now run on Genesis and many now have both Better WP Security and Manage WP installed it's more than a little worrying.
Thanks for your link - oddly I was looking at that exact page yesterday trying to work out what might have done this. I can't work out the logic of whatever error it is removing a few characters from a single template file (which I'm assuming did the trick). I've looked at the error log and all that's there is regarding a core WordPress / Google Oauth thing (apparently a known error) - but that predates the issue anyway.
I've disabled Better WP Security and will monitor the situation to see if it happens again. If it doesn't then, for whatever reason - you'd have to assume that that plugin was the culprit. If it recurs then the next suspect in line is ManageWP.
If anyone has any inspiration regarding this - feel free to add your thoughts!
HelenaBParticipantHi Anitac
Thanks for your comments. I've rechecked security and all is fine there. FTP and other passwords changed too. The error recurred over night...
I have a feeling that this is caused by an interaction of Better WP Security and Manage WP plugins... This started happening once those were installed. Oddly, I've got exactly the same combo working on lots of other sites (including another one on this domain) with no problems.
First five characters of the HTML tag are missing. The rest of the HTML tag and the opening HEAD tag are visible under the admin bar and the rest of the generated page's code visible in the home.php file but without an update button.
I've disabled the security plugin temporarily and will monitor the situation. Weird.
HelenaBParticipantAny suggestions most welcome!
-
AuthorPosts