[solved]blank page after v2.0 install

stephane · Post by **stephane** » Wed Sep 09, 2015 2:04 pm

hello,

I just installed the new v2.0, all goes very well, I can log into the admin panel but....

on the frontend, I have a blank page...

web server's log: PHP Fatal error: Call to a member function encoding() on null

it seems that all the variables assigned in the beginning of the default gabarit (simplex) are not visible in the <head> or in the </__body> section.... (but are visible just after the <doctype>... so in the top.tpl of smarty but not in head.tpl or body.tpl)

no title, no charset (the cause of my error is the call of {$nls->encoding()} in the meta charset tag, in the head of the html doc..... not template_path and no content !!

I tried to add "scope='global'" to the assignement.... it doesn't solve the problem...

sorry for my bad english, hope you understand the problem...

best regards,
stephane

calguy1000 · Post by **calguy1000** » Wed Sep 09, 2015 8:38 pm

Please review the docs site.

We have introduced smarty scopes into 2.0. So there will be work and some learning you need to do when upgrading sites. Particularly those sites using advanced smarty logic and relying on global variables.

Rolf · Post by **Rolf** » Wed Sep 09, 2015 8:48 pm

Might help http://www.cmscanbesimple.org/blog/smar ... e-examples

stephane · Post by **stephane** » Thu Sep 10, 2015 7:31 am

calguy1000: thank you for your answer, I had read somewhere that in 2.0 there was scope with smarty, but my english is very poor so, to understand, it's not easy..... but my php is not so poor so I read your code and it is a very good learning for me (new to cmsms

)

Rolf: thank you for this link, it is exactly the answer to my question

and it solves my problem

thank you all for your work, I'm going to "play" again with v2.0

stephane

swgreed · Post by **swgreed** » Thu Sep 10, 2015 9:08 am

stephane's problem happens to ALL fresh installed installations!

calguy1000 wrote:...some learning you need to do when upgrading sites.

Yes but you should expect that the default simplex frontend theme works out of the box on a new installation (no upgrade)? But instead of that you have to add

Code: Select all

{$nls=$nls scope=global}

in the template coding to make it work.

Can you imagine what kind of impression it makes to someone who wants to try CMSMS for the first time after the default installation displays a blank page?
Right, he will probably choose another CMS...

My developer Page on the Forge · Post by **Jo Morg** » Thu Sep 10, 2015 9:36 am

swgreed wrote:stephane's problem happens to ALL fresh installed installations!

No it does not!

swgreed wrote:you should expect that the default simplex frontend theme works out of the box on a new installation (no upgrade)? But instead of that you have to add.....

Not sure where did you get that idea... please elaborate.

The Development Team made hundreds of installs and upgrades on the most diverse conditions, there was a period of beta testing were possibly thousands of installs and upgrades were tested independently that lead up to a release candidate and ultimately to the final release. There is no way to test all possible combinations of environments and upgrade paths, so there are surely a few issues to be solved.
If the requirements are met, 99% of the installations work out of the box, sorry to disappoint you.
Regarding upgrades, there are too many factors to take into account but most sites can be upgraded as long as they meet requirements and have installed compatible modules.
Calguy1000 statement was specially aimed at upgrades.

swgreed · Post by **swgreed** » Thu Sep 10, 2015 9:56 am

Jo Morg wrote:Not sure where did you get that idea... please elaborate.

Rolfs link implies that solution

Rolf wrote:Might help http://www.cmscanbesimple.org/blog/smar ... e-examples

I suppose that the installation process was tested well, but this error is no hosting issue IMHO.
I tried a full new installation (without the demo content) and got a blank page using the default simplex theme.
(Although this error did not happen with the previous beta test).

The only way to circumvent this issue is either to replace

Code: Select all

<meta charset='{$nls->encoding()}' />

with
<meta charset='utf-8' />
or set the $nls in the global scope as explaned above...

My developer Page on the Forge · Post by **Jo Morg** » Thu Sep 10, 2015 10:37 am

Your last post was way more helpful than the previous one.
Given the steps on how to reproduce it I could confirm it. Should be fixed in next update. Thanks.

CMS Made Simple Forums

[solved]blank page after v2.0 install

[solved]blank page after v2.0 install

Re: blank page after v2.0 install

Re: blank page after v2.0 install

Re: blank page after v2.0 install

Re: blank page after v2.0 install

Re: [solved]blank page after v2.0 install

Re: [solved]blank page after v2.0 install

Re: [solved]blank page after v2.0 install