Closed dimante closed 10 years ago
Is that your frontpage by any chance? If yes, try setting your frontpage to something else. Then browse to the news page. Is the news working now?
If you can answer yes to my questions, then I think I've narrowed the bug down.
@CaMer0n I think this commit breaks functionality https://github.com/e107inc/e107/commit/d3940eafd9c0b9c76571258f9a412d8c89bfb485. The page that is set as frontpage will not render properly. No fatal errors, just looks like a bug in parsing the templates. The source code shows all the html tags properly, there is just no content in the <body>
tags on the page whatever the frontpage is set to. Any other page just works fine.
Let me give that a try and I will confirm.
On Sun, Mar 9, 2014 at 10:51 AM, Tijn Kuyper notifications@github.comwrote:
Is that your frontpage by any chance? If yes, try setting your frontpage to something else. Then browse to the news page. Is the news working now?
If you can answer yes to my questions, then I think I've narrowed the bug down.
@CaMer0n https://github.com/CaMer0n I think this commit breaks functionality d3940eahttps://github.com/e107inc/e107/commit/d3940eafd9c0b9c76571258f9a412d8c89bfb485. The page that is set as frontpage will not render properly. No fatal errors, just looks like an error in parsing the templates. The source code shows all the html tags properly, there is just no content in the tags on the page whatever the frontpage is set to. Any other page just works fine.
Reply to this email directly or view it on GitHubhttps://github.com/e107inc/e107/issues/533#issuecomment-37130090 .
None of the choices work.. When set to news, blank. When set to welcome message, blank. when set to forum I get an error even though the forum is working correctly... My original url is "http://www.dimante.net/news.php" as a custom URL. That rendered my news page with no problems prior to the git pull... I can leave it like this if you have some other ideas to try... To me if I set the "News" radio button it should show news.php it appears this is not happening.
On Sun, Mar 9, 2014 at 11:21 AM, John Gates dimante@dimante.net wrote:
Let me give that a try and I will confirm.
On Sun, Mar 9, 2014 at 10:51 AM, Tijn Kuyper notifications@github.comwrote:
Is that your frontpage by any chance? If yes, try setting your frontpage to something else. Then browse to the news page. Is the news working now?
If you can answer yes to my questions, then I think I've narrowed the bug down.
@CaMer0n https://github.com/CaMer0n I think this commit breaks functionality d3940eahttps://github.com/e107inc/e107/commit/d3940eafd9c0b9c76571258f9a412d8c89bfb485. The page that is set as frontpage will not render properly. No fatal errors, just looks like an error in parsing the templates. The source code shows all the html tags properly, there is just no content in the tags on the page whatever the frontpage is set to. Any other page just works fine.
Reply to this email directly or view it on GitHubhttps://github.com/e107inc/e107/issues/533#issuecomment-37130090 .
To further note, even if I ask for news.php specifically the same blank page is returned..
On Sun, Mar 9, 2014 at 12:01 PM, John Gates dimante@dimante.net wrote:
None of the choices work.. When set to news, blank. When set to welcome message, blank. when set to forum I get an error even though the forum is working correctly... My original url is "http://www.dimante.net/news.php" as a custom URL. That rendered my news page with no problems prior to the git pull... I can leave it like this if you have some other ideas to try... To me if I set the "News" radio button it should show news.php it appears this is not happening.
On Sun, Mar 9, 2014 at 11:21 AM, John Gates dimante@dimante.net wrote:
Let me give that a try and I will confirm.
On Sun, Mar 9, 2014 at 10:51 AM, Tijn Kuyper notifications@github.comwrote:
Is that your frontpage by any chance? If yes, try setting your frontpage to something else. Then browse to the news page. Is the news working now?
If you can answer yes to my questions, then I think I've narrowed the bug down.
@CaMer0n https://github.com/CaMer0n I think this commit breaks functionality d3940eahttps://github.com/e107inc/e107/commit/d3940eafd9c0b9c76571258f9a412d8c89bfb485. The page that is set as frontpage will not render properly. No fatal errors, just looks like an error in parsing the templates. The source code shows all the html tags properly, there is just no content in the tags on the page whatever the frontpage is set to. Any other page just works fine.
Reply to this email directly or view it on GitHubhttps://github.com/e107inc/e107/issues/533#issuecomment-37130090 .
Oh wait, not sure if your issue is related. It's not a blank page on your website, the navigation bar still shows. There's a fatal error somewhere that stops the rest of the page from loading.
Hrm... I have php set to display fatals... Not sure what the error would be..
On Sun, Mar 9, 2014 at 12:10 PM, Tijn Kuyper notifications@github.comwrote:
Oh wait, not sure if your issue is related. It's not a blank page on your website, the navigation bar still shows. There's a fatal error somewhere that stops the rest of the page from loading.
Reply to this email directly or view it on GitHubhttps://github.com/e107inc/e107/issues/533#issuecomment-37132050 .
Try enabling the developer mode and change the url to /news.php?[debug=basic+]
All I do to correct it is put the previous git release on and the page shows..... SO it's something that was introduced later in your development.
On Sun, Mar 9, 2014 at 12:12 PM, John Gates dimante@dimante.net wrote:
Hrm... I have php set to display fatals... Not sure what the error would be..
On Sun, Mar 9, 2014 at 12:10 PM, Tijn Kuyper notifications@github.comwrote:
Oh wait, not sure if your issue is related. It's not a blank page on your website, the navigation bar still shows. There's a fatal error somewhere that stops the rest of the page from loading.
Reply to this email directly or view it on GitHubhttps://github.com/e107inc/e107/issues/533#issuecomment-37132050 .
It would then help to tell us which commit is causing the error.
Have no idea. So I turned debugging on with the previous build and it render this Bad request - destination unreachable - /news.php but the page renders so that is clear as mud. When I put the latest git in here is the result:
Bad request - destination unreachable - /news.php but this time the page does not render... So odd that the same error is returned but shows up in the old.
On Sun, Mar 9, 2014 at 12:15 PM, Tijn Kuyper notifications@github.comwrote:
It would then help to tell us which commit is causing the error.
Reply to this email directly or view it on GitHubhttps://github.com/e107inc/e107/issues/533#issuecomment-37132165 .
Not sure where to go from here. If you have any ideas I would appreciate them :-)
On Sun, Mar 9, 2014 at 12:32 PM, John Gates dimante@dimante.net wrote:
Have no idea. So I turned debugging on with the previous build and it render this Bad request - destination unreachable - /news.php but the page renders so that is clear as mud. When I put the latest git in here is the result:
Bad request - destination unreachable - /news.php but this time the page does not render... So odd that the same error is returned but shows up in the old.
On Sun, Mar 9, 2014 at 12:15 PM, Tijn Kuyper notifications@github.comwrote:
It would then help to tell us which commit is causing the error.
Reply to this email directly or view it on GitHubhttps://github.com/e107inc/e107/issues/533#issuecomment-37132165 .
Is it expecting news.php to be somewhere other than the root of the site?
On Sun, Mar 9, 2014 at 12:32 PM, John Gates dimante@dimante.net wrote:
Not sure where to go from here. If you have any ideas I would appreciate them :-)
On Sun, Mar 9, 2014 at 12:32 PM, John Gates dimante@dimante.net wrote:
Have no idea. So I turned debugging on with the previous build and it render this Bad request - destination unreachable - /news.php but the page renders so that is clear as mud. When I put the latest git in here is the result:
Bad request - destination unreachable - /news.php but this time the page does not render... So odd that the same error is returned but shows up in the old.
On Sun, Mar 9, 2014 at 12:15 PM, Tijn Kuyper notifications@github.comwrote:
It would then help to tell us which commit is causing the error.
Reply to this email directly or view it on GitHubhttps://github.com/e107inc/e107/issues/533#issuecomment-37132165 .
Please hang on for a while, I'm not available all day haha :)
Totally understood :-)
On Sun, Mar 9, 2014 at 12:47 PM, Tijn Kuyper notifications@github.comwrote:
Please hang on for a while, I'm not available all day haha :)
Reply to this email directly or view it on GitHubhttps://github.com/e107inc/e107/issues/533#issuecomment-37133044 .
Using the latest version from Github, try replacing the e107_core/templates/header_default.php file with the following: https://raw.github.com/e107inc/e107/0df0f49cc01f37971075d3fbc51cdf8231a30042/e107_core/templates/header_default.php Then check and see if the issue is resolved.
No change.
On Sun, Mar 9, 2014 at 5:26 PM, Tijn Kuyper notifications@github.comwrote:
Using the latest version from Github, try replacing the e107_core/templates/header_default.php file with the following: https://raw.github.com/e107inc/e107/0df0f49cc01f37971075d3fbc51cdf8231a30042/e107_core/templates/header_default.php Then check and see if the issue is resolved.
Reply to this email directly or view it on GitHubhttps://github.com/e107inc/e107/issues/533#issuecomment-37142018 .
Compare your current base code to this news.php it is the difference between what this file has and what was changed in the current that cause the problem for me. The attached news.php works on my site and I can see my page.
On Sun, Mar 9, 2014 at 6:38 PM, John Gates dimante@dimante.net wrote:
No change.
On Sun, Mar 9, 2014 at 5:26 PM, Tijn Kuyper notifications@github.comwrote:
Using the latest version from Github, try replacing the e107_core/templates/header_default.php file with the following: https://raw.github.com/e107inc/e107/0df0f49cc01f37971075d3fbc51cdf8231a30042/e107_core/templates/header_default.php Then check and see if the issue is resolved.
Reply to this email directly or view it on GitHubhttps://github.com/e107inc/e107/issues/533#issuecomment-37142018 .
It also seems the site has become more complicated than it needs to be. There is a difference between what loads at the base url... I want the site to just load news.php as the base page that loads... That's what happened in the old version I am just confused as to what the base url is loading vs news.php with the base url the news items load but no menus to the right... Just confusing to me and I really want to understand how it works...
On Sun, Mar 9, 2014 at 7:59 PM, John Gates dimante@dimante.net wrote:
Compare your current base code to this news.php it is the difference between what this file has and what was changed in the current that cause the problem for me. The attached news.php works on my site and I can see my page.
On Sun, Mar 9, 2014 at 6:38 PM, John Gates dimante@dimante.net wrote:
No change.
On Sun, Mar 9, 2014 at 5:26 PM, Tijn Kuyper notifications@github.comwrote:
Using the latest version from Github, try replacing the e107_core/templates/header_default.php file with the following: https://raw.github.com/e107inc/e107/0df0f49cc01f37971075d3fbc51cdf8231a30042/e107_core/templates/header_default.php Then check and see if the issue is resolved.
Reply to this email directly or view it on GitHubhttps://github.com/e107inc/e107/issues/533#issuecomment-37142018 .
This sounds like the same issue as what started off my issue, #525 which I subsequently "killed" due to my trying to reinstall e107. My current news-page, after a fresh-install, doesn't look like how it should though. No other people are suffering from these issues?
Here is what the landing page displays: [image: Inline image 1]
Here is what I think it should display (And does display when I click home): [image: Inline image 2]
I don't understand this new layout. I want the landing page to be news.php with the right hand menus.... Is this something I am setting up wrong? Just not sure.
On Mon, Mar 10, 2014 at 8:35 AM, brhahlen notifications@github.com wrote:
This sounds like the same issue as what started off my issue, #525https://github.com/e107inc/e107/issues/525which I subsequently "killed" due to my trying to reinstall e107. My current news-page, after a fresh-install, doesn't look like how it should though. No other people are suffering from these issues?
Reply to this email directly or view it on GitHubhttps://github.com/e107inc/e107/issues/533#issuecomment-37182096 .
Not a solution to this problem but rather an update. It turns out that the error I was talking about is caused by a theme that I am developing. I therefore think that the issue you guys are having is unrelated to mine.
So... I just pulled the latest git (today 5/15/2014) it still caused my news.php file to render blank unless I replaced it with my old one.
I can't help, but I think that you had to change something else. I tried this (put news.php as my frontpage), no problem. In clean install there is welcome message and then news. I deleted WM, but it still works.
Do you use bootstrap3 theme, don't you? What layout do you have for frontpage? Jumbotron home?
Jumbotron sidebar right.
On Fri, May 16, 2014 at 5:02 AM, Jimako notifications@github.com wrote:
I can't help, but I think that you had to change something else. I tried this (put news.php as my frontpage), no problem. In clean install there is welcome message and then news. I deleted WM, but it still works.
Do you use bootstrap3 theme, don't you? What layout do you have for frontpage? Jumbotron home?
— Reply to this email directly or view it on GitHubhttps://github.com/e107inc/e107/issues/533#issuecomment-43315859 .
If you want to use set front-page preferencies, you need to set FRONTPAGE to some of your layout (in theme manager as visibility filter) or use only default. But what do you use as default layout then? Tested all combination that occured me, everything works. Don't you change something in theme.php?
So do this:
// Set the Values for the social shortcode usage. $socialArray = array('url'=>e107::getUrl()->create('news/view/item', $news, 'full=1'), 'title'=>$tp->toText($news['news_title'])); e107::getScBatch('social')->setVars($socialArray);
This is the only difference in git news.php and my news.php when this code is not present everything works fine... Ideas?
On Sat, May 17, 2014 at 4:37 AM, Jimako notifications@github.com wrote:
If you want to use set front-page preferencies, you need to set FRONTPAGE to some of your layout (in theme manager as visibility filter) or use only default. But what do you use as default layout then? Tested all combination that occured me, everything works. Don't you change something in theme.php?
So do this:
- set FRONTPAGE back to jumbotron home and check black page
- if there is blank page, change content of your news - use only text Could you check content of your news (my way: to add button html source in tinymce - in mainadmin.xml in tinymce plugin)
— Reply to this email directly or view it on GitHubhttps://github.com/e107inc/e107/issues/533#issuecomment-43402452 .
I have them there too. Did you set some socials in your admin?
i do notice my server spitting out errors : (seems related? ) error seems to appear in a version from april
Call to a member function setVars() on a non-object in /home/gabber/public_html/v2/news.php on line 825
That's indeed an error that would cause the blank page. Let's see if I can figure this out.
I get this with firefox and the e107 debugger plugin...
Couldn't Load: e107_core/shortcodes/batch/social_shortcodes.php with class-name: social_shortcodes and pluginName
And I just looked on GIT and this file does not exist there either... So this is certainly a problem :-(
@CaMer0n Can you take a look here?
Is that file supposed to exist?
Try this debug: news.php?[debug=bbsc+] Search for 'social' in the debug info at the bottom. The correct info is: Array ( [type] => class [path] => e107_plugins/social/e_shortcode.php [class] => social_shortcodes ) Can you find this info? Have any changes been made to the bootstrap3 theme? Try doing a plugin scan (admin->database) and retesting as above.
I believe this one is resolved
Array ( [type] => class [path] => e107_plugins/social/e_shortcode.php [class] => social_shortcodes ) And this path does exist. So the problem no longer exists.
@dimante So this started working again after a plugin scan? Please elaborate a bit on how you fixed it.
Apparently it got fixed with one of the git updates. The original post shows the path it was looking for in regard to the shortcodes and it did not exist....
On Thu, May 22, 2014 at 4:56 PM, Tijn Kuyper notifications@github.comwrote:
@dimante https://github.com/dimante So this started working again after a plugin scan? Please elaborate a bit on how you fixed it.
— Reply to this email directly or view it on GitHubhttps://github.com/e107inc/e107/issues/533#issuecomment-43949207 .
So the social plugin folder was not uploaded on your installation yet right? And after uploading it, the error was fixed?
If this is the case, please completely reupload a fresh zip from Github and overwrite all the current files. Issue #590 seems to be caused by corrupted/incorrectly uploaded or missing files.
No at first the error I got was looking for this:
Couldn't Load: e107_core/shortcodes/batch/social_shortcodes.php with class-name: social_shortcodes and pluginName
well that path does not exist.
Is there something I can do to insure that no old e107 files exist out there? Let me try flushing the install folder and only placing files from the github download.. Give me about 20 mins...
On Thu, May 22, 2014 at 5:04 PM, Tijn Kuyper notifications@github.comwrote:
So the social plugin folder was not uploaded on your installation yet right? And after uploading it, the error was fixed?
If this is the case, please completely reupload a fresh zip from Github and overwrite all the current files. Issue #590https://github.com/e107inc/e107/issues/590seems to be caused by corrupted/incorrectly uploaded or missing files.
— Reply to this email directly or view it on GitHubhttps://github.com/e107inc/e107/issues/533#issuecomment-43949899 .
Ok I got that. What did you change to fix the issue?
Is there something I can do to insure that no old e107 files exist out there?
Unfortunately the possibilities of having such check on shared-hosting platforms is pretty much not achievable (technically). Ideally you would simply clone the e107 repository over and you can simply issue a git pull
to make sure all the files are up to date.
Latest git version and fresh install for me fixed this. Haven't done a "full" git clone, but just an update of a current git version.
Alright, seems this was a social plugin issue. We should be good now. Please re-open if necessary.
Just thought I would mention with todays update from git my news page is blank......