Hi,

I am having the same issue: dashboard not loading and a HUGE error file is created with the following "/home/kkutt/public_html/libraries/joomla/feed/factory.php on line 71".
I followed your suggestion of removing the feed line and this has resolved the issue. I have used your component a number of times before on other sites at the same server, without issue. Let me know if it would help to provide further information.

Cheers,


Liz

Hey Guys,
Can someone of you test the latest developer version and let me know if it now works on those servers?

Regards,
Daniel

Hey Garth,
You can see the feed for yourself: http://compojoom.com/blog/tags/listings/cmc?format=feed&%3btype=rss -> it works and it is not faulty.

If you have a look at the joomla code you'll see that the calls to the xml:read() function is surrounded by a try catch construct. If there is an error in reading the feed, PHP returns an error, it is catched in the catch block and this error is output on the screen.
In this particular case, on that server -> php just breaks in this function and doesn't manage to return any error. Posible reasons for this is a firewall that is misconfigured...

If you are experiencing the get_address issue mentioned inthe joomla thread, then do a google search: http://www.google.de/search?q=php_network_getad...MOxZVIWYNo-KOqjVgKgC

All the threads that follow say it - your server is not configured properly...

Regards,
Daniel

Go to: administrator\components\com_cmc\views\cpanel\tmpl\default.php
line 82 you have:

<?php echo CompojoomHtmlFeed::renderFeed('https://compojoom.com/about/blog/tags/listings/cmc?format=feed&type=rss'); ?>

delete this line and the dashboard should load after that.
What this line tries to do is -> load the following url: https://compojoom.com/about/blog/tags/listings/cmc?format=feed&type=rss and then show the results from it in a list...
Nothing crazy about it. Why it breaks on your server and why it doesn't break on others is currently beyond me. You can read my comments above. As your hosting told you and as I wrote above it breaks in in /home/newhopec/public_html/libraries/joomla/feed/factory.php on line 71 On this line we have XMLReader::read() -> that is a standard PHP function and it shouldn't cause this. But for some reason it does... My only guess is corrupted php libraries...

Regards,
Daniel

I have set this up on an entirely different site to try out again (same sever though) and disabled the code as you described above. Didn't change anything - still had the same problem and same error log.

When I lookup other error reports on the internet I see people having similar problems however finding other plugins which don't hare this problem - they use the same server and similar plugins to achieve the same result. I have gone back to my server and mentioned this to them as possibly being corrupt PHP files but I'm going to go out on a limb here and say that I highly doubt that this is going to be the case.
http://forum.joomla.org/viewtopic.php?f=706&t=841620&view=previous

On siteground they were helping another user with a similar problem and their input was:
"The root of this problem is most likely a faulty extension not parsing XML feeds properly due to an invalid XML source."

As people seem t have had similar problems going back a year or so, I'd doubt it has much to do with the PHP version, but fyi this Namecheap server is running PHP5.3.29
I'll setup a site on H9 with the J3.3.6 and PHP5.5.34 and try it out.

cheers
Garth

Hi,
I am aware that the ~E_STRICT determination in PHP .ini is an error logging variable. It is probably a default on the new PHP 5.4 servers to have error logging for STRICT infringements in strict coding principles turned off by default (however most of my setups use php.ini with reduced logging setting but obviously not ~E_STRICT hence why I'mhaving to edit these files now).

That was not the point I was making Daniel.

What I am saying is that, unless it is some kind of major oversight by either the PHP makers or Namecheap and Hostnine (since those are the two companies that I have servers with), then the appearance of this logging event shows greater focus on adherence to better / stricter coding guidelines in PHP 5.4 indicates that they are getting serious about using strictly correct PHP coding principles. I mean, why would they start including the logging of 'errors' based on code that doesn't follow STRICT guidelines as default logging unless they want to start making people aware of what needs to be changed to bring coding into line with stricter coding techniques. PHP aren't the only platform to be enforcing stricter coding guidelines now.

Hence it is pointing to a stricter adherence to strict PHP coding guidelines - and maybe in so doing, PHP is now starting to throw up actual errors on coding that doesn't follow some of these guidelines.

As I said, I wouldn't know, nor would I know whether the code you referred to fits within the guidelines, but since there is 'smoke' in this direction, it might be where the 'fire' is.
Best of luck with it.

No, it cannot be the E_STRICT as this is just a reporting thing and I have it enabled on my dev. machine (which also run 5.4). It must be something else.

Regards,
Daniel

Thank you for the code suggestion. I have moved onto a different plugin for now, however if I have a need I to try this plugin next time, I will try it out if there isn't a fix in the meantime.

Methinks it has to do with the PHP 5.4 strict php setting that Namecheap servers have implemented, since I've noticed my old php.ini settings which do not include an error logging setting of ~$E_STRICT are pumping out errors based on non-compliance with strict compliance in Joomla. It is probably requiring compliance to new PHP 5.4 rules.

You'd know better than I. Thanks for the reply.

And if you look at our renderFeed function you'll see that we are looking for an exception. We try to load the feed, but if it doesn't work, then we show a text "feed couldn't be loaded". The normal behavior of JFeedFactory is to throw an exception when something goes south... But on your servers this doesn't happen & that is why you are confronted with that error
I'm sure that there are others that suffer from this issue - the question is what to do about it? We've done our part to encapsulate the code and capture an error. Unfortunately the standard php code for some reason doesn't behave correctly & I have no clue what to do.
If you guys have an idea - feel free to share!

Go to: administrator\components\com_cmc\views\cpanel\tmpl\default.php
line 82 you have:

<?php echo CompojoomHtmlFeed::renderFeed('https://compojoom.com/about/blog/tags/listings/cmc?format=feed&type=rss'); ?>

delete this line and the dashboard should load after that.
What this line tries to do is -> load the following url: https://compojoom.com/about/blog/tags/listings/cmc?format=feed&type=rss and then show the results from it in a list...
Nothing crazy about it. Why it breaks on your server and why it doesn't break on others is currently beyond me. You can read my comments above. As your hosting told you and as I wrote above it breaks in in /home/newhopec/public_html/libraries/joomla/feed/factory.php on line 71 On this line we have XMLReader::read() -> that is a standard PHP function and it shouldn't cause this. But for some reason it does... My only guess is corrupted php libraries...

Regards,
Daniel

I am running our (many) sites on a server with the large US company, Namecheap.

As I am having the same issue off a simple clean install with a client site of ours, and knew that someone else would be experiencing it as well, I promptly found this forum entry. This is Namecheap's reseller support reply when I queried them on this issue.

-------
We have investigated the issue and see the following errors in our error log file:
[Wed Sep 24 15:12:18 2014] [error] [client 205.251.129.126] Fatal error: Allowed memory size of 176160768 bytes exhausted (tried to allocate 165939201 bytes) in /home/newhopec/public_html/libraries/joomla/feed/factory.php on line 71, referer: http://newhopeforlife.org.au/administrator/index.php

It means that when it tries to open CMC page in your admin area, that process tries to allocate more memory that it is allowed in your PHP settings. It is possible to increase memory_limit, however, there is no sense doing it in this separate case, because high memory usage of that process is caused by huge amount of failures of your script. There is huge amount of common records in error log file located at public_html/administrator:

[24-Sep-2014 15:09:31 America/New_York] PHP Warning: XMLReader::read() [<a href='xmlreader.read'>xmlreader.read</a>]: An Error Occured while reading in /home/newhopec/public_html/libraries/joomla/feed/factory.php on line 71

Those errors are generated when you try to open CMC in admin area. This issue seems to be related to code_debugging, because we do not see any hosting issues at the moment. Unfortunately, we do not provide code debugging support. Such cases are not related to our hosting services. Code debugging includes testing for errors or determining the cause of an error and fixing it. The reason we do not provide such options is that such cases refers to site development service and not to hosting related one. We recommend you to contact webmaster or the developer of the code to resolve the issue.

Feel free to contact us again in case of any questions or issues.
-------

So, we know where the issue is, and I would like to know if this code is necessary for it to run, and if there is a simple way to disable this code so that I can implement CMC.
thank you
Garth Penglase

ps. if two of us are having problems with this out of the box and are willing to report it, you can bet your life that there are others, probably many, that are experiencing the same, but can't be bothered so just uninstall it and move on, which is what I was going to do but found that AllChimpRegister hasn't yet upgraded for J3.x yet.

yep, that comes from the xmlreader which is a php library bundled with php. Disable the call to the feed in dashboard default.php that I mentioned above and the dashboard will load.

There is definetly something wrong with your php/apache installation, but I have no idea what. The script should not terminate white it is reading the feed & it doesn't terminate on 1000 of other pages.
What I would suggest is -> backup of the site, try it on localhost or on a different server. If it is working, then the problem is in the specific configuration of the server.
I have the component running on few different servers and I haven't come accross this. My guess is that there is something corrupt somewhere. Maybe re-compiling php would help.

Regards,
Daniel

It looks like when you edited the factory.php file it went blank too. I commented out the same lines but the log definitely shows that it's something to do with reading the feed from your component. I wonder... can we look at that?

[04-Sep-2014 14:03:20 America/New_York] PHP Warning:  XMLReader::read() [<a href='xmlreader.read'>xmlreader.read</a>]: An Error Occured while reading in /home/user/public_html/libraries/joomla/feed/factory.php on line 71

I manually went into the terminal as root and pasted the code into the file. It's there and now we have something but... well, you'll just have to see if you can login to the admin and view it again.

administrator/components/views/dashboard/tmpl/default.php

I wanted to write dashboard view and not dashboard.php sorry.

I checked the server and the files from the component download directly from your site and I don't find dashboard.php at all. Am I missing something? Yes, the server has free space and this account is not above quota. Space is fine.

Well, actually something is going on on your server. I tried to save the view file of the dashboard.php and now it saves as an empty file. Do you have enough disc space on the server? Because it seems that it is writing to the file, but when I download the file from the server it is empty.

Regards,
Daniel

So, I had a look at your site and you need to figure out why error reporting is not working. It is not just in cmc, but everywhere. Also you have wrong valued for the error_log -> it should be the path to the log and not just error_log.

Other than that the error seems to occur in libraries/joomla/feed/factory.php line 71 .
This is where I was able to track it. After that line no die() statement was executed. But what exactly happens there is beyond me, since I cannot see the error messages.

We've commented out the line that tries to read the rss from our site and the dashboard is now loading, but I would strongly advise to get down at the bottom of this as this will cause you more headaches in the long term.

Regards,
Daniel

Something is blocking the error output (ini_set function or something) can you provide FTP access also?

Kind regards,

Yves

Email sent.

No, i think we have to look at it ourself - can you create a super admin account for us? (Send the credentials to contact-us@compojoom.com), then we have a look.

Kind regards,

Yves