-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PHP error - website down #24
Comments
I have the exact same issue. Started about the same time as the person above which makes me think something is broke on at a source server. I have it installed on a 2.5 site and a 3.0. Has yahoo weather API changed? Could this be the reason nether module is working now? |
Same issue, having "?" for the data (on Joomla! 3.4.8) |
I have found this solution |
@InformatiqueProg - thank you for your pull request :) I've also applied some other fixes which could cause issues and you can now download v.1.7.2 from: https://github.com/GavickPro/Weather/releases/tag/v.1.7.2 |
I've updated the module and check the help.php file and it's showing the xml link correctly. However, I'm still getting the question mark for everything. Anything else I need to change or update? I'm on a Joomla 3.4.8. |
@julandesign - please check if the weather works for other locations like new york - maybe there is no weather data for your area or you have provided wrong WOEID number. |
Hello ,
I have joomla 2.5 and the latest weather module 1.7. I receive a blank page, the website braeks comletelly down wherever the module is active, with this message:
Parse error: syntax error, unexpected ':' in /home4/eastcret/public_html/silogos/libraries/joomla/utilities/simplexml.php(386) : eval()'d code on line 1
Fatal error: Call to a member function attributes() on a non-object in /home4/eastcret/public_html/silogos/modules/mod_weather_gk4/helper.php on line 377
Please, what can be wrong here?? My server maybe?? The website worked perfectly until 2-3 days ago. Sudenly we have this error.
Thank you for your help!
The text was updated successfully, but these errors were encountered: