TOPIC: Blank Page

Go to: administrator\components\com_cmc\views\cpanel\tmpl\default.php
line 82 you have:delete this line and the dashboard should load after that.
What this line tries to do is -> load the following url: compojoom.com/about/blog/tags/listings/c...at=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

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!

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.

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

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.

Daniel Dimitrov wrote: 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&amp;type=rss'); ?>

delete this line and the dashboard should load after that.
What this line tries to do is -> load the following url: compojoom.com/about/blog/tags/listings/c...at=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.
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

Hey Garth,
You can see the feed for yourself: 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: 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

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

Regards,
Daniel

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