By Sean Carney on Monday, 05 June 2017
Posted in Technical Issues
Likes 0
Views 866
Votes 0
I am unable to leave a comment on our web site now in reply to somebody else's comment and I am hoping you might have an idea why? I am getting other comments from spammers so it is a puzzle to me. I get a little error message that says "Internal Server Error" just above the Leave your comments box.

I also got a message that my recaptcha had expired a couple times but then when I refresh the page I can try to submit again but still get the Internal Server Error. Any ideas about this would be greatly appreciated.

This is the url where I was trying to leave a comment:

https://www.drcarney.com/index.php?option=com_easyblog&view=entry&id=1656&Itemid=317

This is another url to the same page:

https://www.drcarney.com/blog/entry/dietary-isoflavone-intake-and-all-cause-mortality-in-breast-cancer-survivors-the-breast-cancer-family-registry

This is the comment I was trying to leave as Sean Carney:


Here is an article titled Should we be Concerned about Phytic Acid? that is not particularly about soy but which you may find helpful:
https://www.drcarney.com/blog/entry/should-we-be-concerned-about-phytic-acid

And, here is an blog about Debunking the Anti-Soy Myths that you also might find interesting.

The following page is a Search for the term Soy on this web site that will provide many studies that have been done regarding soy. The bottom line is there is no need to worry about this.

Hope this is helpful.
Sean
Hi Sean,

As I try to comment I'm hitting this error:
0 - Too few arguments to function KomentoNotification::getSubscribers(), 1 passed in /mnt/data/vhosts/casite-505587.cloudaccess.net/httpdocs/administrator/components/com_komento/includes/push/push.php on line 95 and exactly 2 expected


Seems like there is a bug in our end. I've fix this in the file:
.../administrator/components/com_komento/includes/push/push.php
Can you please give it another try?

This fix has been included in our repository and will be included in our next release.
·
Monday, 05 June 2017 13:30
·
0 Likes
·
0 Votes
·
0 Comments
·
That fix seems to have worked. Thank you.

Sean
·
Monday, 05 June 2017 22:14
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for updating Sean, glad that your issues are resolved now
·
Tuesday, 06 June 2017 04:48
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post