Forum Replies Created
Thanks for the feedback. First of all I use BPS Pro that has a login security system. I was alerted to the fact that an 'unusual' and active username was directly used to login which meant it was likely divulged in some way. To my surprise I found the links as described above for the author that gave away the culprit login details in the source code of pages.
I then removed these using the Simple Edits plugin that by default shows the authorlink in the code and I also changed this in Nicks Amplified Feature plugin. Both Genesis out of the box, Simple Edits and Nicks plugin display by default a link that has the authorname in it.
@wpperform I do not agree with the approach that says this is default behaviour of WordPress since it 'IS' in the themes and plugins that this information is generated and then displayed, WordPress is just the basis. I would only be paraphrasing what was discussed on the BPS forum anyway... But themes and plugins shouldn't be doing this
BTW you only need to check the demos on studiopress to see there are several themes that show the author info (ie http://domainname.com/theme/author/admin !)
@braddalton I have removed all the occurrences on my main sites, was it to check?
Wow cool thanks essaysnark and there look to be some interesting functions there.
Hope it works with Dynamik
I have a lot of problems with W3TC and found it had far more functions that I didn't use than WP Super Cache. I had tried a plugin that removes comments in general but then some of them are used in the code so it breaks the page...
Would be nice to have an option in the Genesis framework to turn them off once development has stopped to reduce page size and the comments don't serve any purpose other than for dev work IMHO
Sorry I hadn't refreshed the page and seen your post in between time. Also my mistake it is a download with the other theme I mentionned and not through Genesis, so I'll take it up with them. Although it may just be a 3.6 incompatibility that needs to be fixed.
Oh, your point just made me check and I've just realised that the test server is using a 3.6 beta 2 version of WordPress to check everything before launch and see if there were any issues. Could it be that the Nivo doesn't work with it (yet)?
I'll check with the Nivo authors about it
Thanks again and impressive response time 😉
Good point. Unfortunately when I just tried that it was the same issue, I activated the minimum child theme and it was the same issue.
It must be some code that the nivo slider is trying to insert into the visual editor area above the content area where all the icons to allow for sliders to be added into posts. I'm guessing here since I have never seen it other than in a screenshot!