Whitegoodshelp

It appears to have stopped the duplicate emails. So if your duplicate emails are to different addresses it could be the same issue I had. I’ve now re-ticked the notify me when anyone posts a comment but still only get one email to moderate a comment (which is great) but no notification of new comments after.

I’m having exactly the same issue. Duplicate “please Moderate..” emails with exactly the same time stamp pn. Plus at the same time I now no longer receive an email telling me of a new comment after I’ve moderated it and allowed it.

I have just noticed that both the emails go to different email addresses of mine. I recently changed the email address in General Settings whereas before I had the same email address that I use on my profile.

I’ve always had all the boxes ticked mentioned by 123milliseconds but this issue has only just occurred. So I’m wondering if the system didn’t send 2 emails to the same address, but now I’ve changed the admin email address it is notifying me as the admin and me as the author.

I’ve just returned my admin email as defined in General Settings to be the same as my author address as it was before and will report back if this affects the issue.

Hello mtekk: I just restored the breadcrumb plugin folder and reactivated the plugin, which I’m glad to report now works ok. I can only assume there was some delay between them sending me the email telling me the php was upgraded and me actually using it.

I agree that 5 years seems a ridiculously long time to keep a version although they say they keep it up to date with security upgrades. I don’t know how much php changes but clearly things do normally function ok with a 4 year old version as your plugin is the only issue I’m aware of on all my sites and Blogs.

It still seems a risky thing to make the plugin require a pretty up to date php version as there must be many with older versions but I’m glad to have the plugin back because I think it’s useful and good for seo to have a breadcrumb trail.

Andy

Hello mtekk: Thanks for your response. It was a year or two back. I think it was not long after I’d started using it and there was an update. I said previously that the earlier incident caused a blank page but I should have said it caused my header and sidebar to be displayed but no content. If you didn’t get any other reports it may have been something peculiar to how I had it installed or my wordpress skin. All I remember was I had to move the calling code somewhere else.

I apologise for using the phrase “always breaking my blog”, I was a bit angry at losing my blog. As it is a major part of my livelihood I get quite stressed if it goes down.

Regarding this current issue if it is WordPress’s fault it’s a very serious bug that needs fixing. As I said before surely the number one thing to be avoided is for a Blog to be taken offline.

I contacted my hosting company and they said –

“5.1.6 is an old verison in upstream terms. However it is the chosen version for CentOS 5 to distribute. Because CentOS versions are released and supported for 5 years, towards the end of their life the default versions of applications may seem old, but are kept up
to date security wise by back-porting bug fixes.

CentOS 6 is due out in the next few months which will distribute PHP 5.3.x, but again this will be supported for 5 years, and will seem out of date by the time we get to 2015!”

I don’t know if that’s true or not but if so there could be a lot of people with an old version of php.

When I received the message “I have upgrade PHP which is now at version 5.2.16.” I tried breadcrumb again and exactly the same thing happened. I just got a blank page with the same warning that my php version was too old and had to delete the breadcrumb folder again. I wondered if was somehow a caching issue but I tried reloading my blog with a control + refresh.

I think this plugin is one of the essential plugins and I don’t like being without it.

Hello mtekk. I upgraded it once before and my Blog just displayed a blank page. It turned out that the code had been changed and I had to move the lines of code calling the script from its previous place to another location to get it to work.

Regarding this present incident, I wouldn’t object to you requiring any version of php, or even changing things within the code that made it only work under ridiculously rare circumstances. It’s a free plugin and I find it very useful but you can change it however you like. My objection is if an author changed criteria so that when their users update it, it doesn’t just not work but it completely brings down the Blog. I couldn’t even get back into my control panel to disable the plugin and if I hadn’t thought to use ftf to delete the breadcrumb folder I would have been left without a working Blog.

I can only assume it was an unexpected situation from your point of view and surely the plugin isn’t deliberately written knowing it will cause a fatal error if it can’t find the “right” version of php? I thought error handling in software allowed contained reactions to not finding the right environment to run in?

I can only assume you had no idea the blog would be brought down if the wrong php version was installed or otherwise you would have not allowed the plugin to install unless it had checked for the right version first or at least warned people not to update it unless they had checked they were running the later php version. I updated it using automatic update.

I’ve now had V5.2.16 installed and get exactly the same error

This plugin is always breaking my Blog. It’s done it more than once before but never with such catastrophic consequences as locking me even out of my control panel so I couldn’t disable it. I had to connect by ftp and delete the breadcrumb folder to get back into my control panel and restore my blog.

This plugin just took my blog offline completely without warning. After updating the plugin it completely locked me out of my control panel. This is totally unacceptable. The only way I could disable it was to connect by ftp and delete the breadcrumb plugin folder.

The excuse that our php version is too old is a joke. All my other dozens of plugins work fine with it as does WordPress itself. How can an author update their plugin to require a certain version of php and then completely take down the blog when it finds an older version?

OK. I disabled all my plugins but the fault remained. I then re-enabled them all except Search unleashed, which was giving a fatal error after upgrading it before I upgraded to 2.8.2 and the fault disappeared.

Strong evidence that the issue was caused by this search plugin.

Oops. I forgot to include the url
https://www.whitegoodshelp.co.uk/wordpress/

I’m using a customised mw1.2 theme but I thought all the display instructions were within the themes files in the content folder which I left in tact.

I’ve found a fix that worked for me. I only just discovered I have this problem too as I use Firefox browser and everything worked fine. However, I just found whilst using Internet Explorer that none of my comment links actually went through the comments.

All my links which I’d customised to say “no comments yet what do you think?” just went to the top of the article from the index page. If I scrolled down to the bottom of an article and clicked the comment link nothing happened.

After finding this thread and being disappointed the answer was not here I tried to fathom it out myself. I remembered reading in a book some years back that when creating HTML anchor links it is best to use a specific method which I had always used.

Checking the comments.php file I could see the use of <a href="#respond">Leave your comment</a>

I found that the anchor link for responding to the comments link was as follows <a name="respond"></a>

I changed this link to <a name="respond" id="respond">&nbsp;</a> And now my links work in Internet Explorer.

Can you explain why, as the instructions say to put <?php session_start(); ?> in wp-login which appeared to work OK?

Thanks. They don’t do any damage because they can’t get any spam past the spam filters but it’s annoying when you can’t be sure which are genuine members.

I have solved the problem

It was caused because I didn’t have a writable .htaccess file in the root folder. I have never had an .htaccess file in my blog so I dodn’t realise the significance. It seems that no .htaccess file doesn’t cause any problems as long as your index.php file is inside the wordpress folder. After moving it to the root the wordpress script seems to have needed to write something to this missing file to update all the links.

Sorted it!

I didn’t have a writable .htaccess file in the root. I knew this from the start but didn’t realise its signigficance because in my other wordpress blog I didn’t have one either and that worked fine for the last 12 months.

I presume that moving the index file to the root away from the wordpress folder needed a .htaccess file to write some chages to?

By default the .htacces file I created was chmod to 644. I changes it to 777 – does anyone know if this is what it should be set to please?

BTW I created the .htaccess file in notepad using the text shown at the bottom of my settings page in admin, which I eventually noticed.