Why is frontend blank

[Agaton]

I use VM 2.0.22a plus joomla 2.5.14

Every time i upgrade to vm 2.0.22c the front end for vm is completely blank.

I initially thought this may be a Joomla template issue but it occurs on every template i use. I also considered that the overrides may be the issue so I have disabled them....

Any suggestions.

[Maxim Pishnyak]

http://dev.virtuemart.net/projects/virtuemart/files
d subversion

[Agaton]

http://dev.virtuemart.net/projects/virtuemart/files
d subversion

Thanks.

If you are saying that d is the answer to the problem then unfortunately it isn't... once d is installed same thing happens.... in fact install 2.0.22b,c or d and the vm frontend is completely blank... When i revert back to 2.0.22a its fine.

I dont just mean the vm frontend i mean when you click a vm link the whole browser page is white.

note: no code is being generated at all in the browser, as I mentioned this is on two sites both using different templates, one is my own and another purchased from joomladesigns.....

[jenkinhill]

Try this: In VM configuration/templates set Default template and the Category Template to "Use joomla default" in Config/Templates.

[Agaton]

Try this: In VM configuration/templates set Default template and the Category Template to "Use joomla default" in Config/Templates.

That setting is already in place

[Agaton]

Are there any more suggestion, if this can happen on two sites completely different joomla templates. There must be a flaw in the upgrade or i'm missing something drastic.

[Maxim Pishnyak]

Every time i upgrade to vm 2.0.22c the front end for vm is completely blank.

You need to turn on displaying errors in your Joomla config and tell us then what error did you have at 'blank' page in your web site.

[Agaton]

Every time i upgrade to vm 2.0.22c the front end for vm is completely blank.

You need to turn on displaying errors in your Joomla config and tell us then what error did you have at 'blank' page in your web site.

You do mean debug, yes?

[Maxim Pishnyak]

Error Reporting

[Agaton]

Error Reporting

That has been enabled and I only get the same error messages that appear on the joomla pages that work....

Strict Standards: Declaration of OPCloader::logged() should be compatible with that of VirtueMartViewCart::logged() in /var/www/vhosts/testdomain.co.uk/httpdocs/components/com_onepage/helpers/loader.php on line 22

Strict Standards: Declaration of OPCloader::getModel() should be compatible with that of JView::getModel() in /var/www/vhosts/testdomain.co.uk/httpdocs/components/com_onepage/helpers/loader.php on line 22

Strict Standards: Only variables should be assigned by reference in /var/www/vhosts/testdomain.co.uk/httpdocs/templates/thathelped/config.php on line 11

Strict Standards: Only variables should be assigned by reference in /var/www/vhosts/testdomain.co.uk/httpdocs/templates/thathelped/config.php on line 12

Deprecated: Function ereg_replace() is deprecated in /var/www/vhosts/testdomain.co.uk/httpdocs/templates/thathelped/config.php on line 38

Notice: Undefined variable: logoImage in /var/www/vhosts/testdomain.co.uk/httpdocs/templates/thathelped/config.php on line 165

Warning: getimagesize() [function.getimagesize]: Filename cannot be empty in /var/www/vhosts/testdomain.co.uk/httpdocs/templates/thathelped/config.php on line 165

I would assume from this that something has changed in VM2.0.22b,c,d that was not present on VM2.0.22a, as all non VM pages work perfectly.

Any suggestions....

Question: Has there been any significant changes to VM view templates?

[jenkinhill]

Looks like a problem with one page checkout.  OPCs need updating for 2.0.22c/d - at least one 3rd party developer has released an updated version.

VM templates are changed as of 2.0.22c  (not before) for security fixes.  http://virtuemart.net/news/list-all-news/446-important-security-release-vm-team-at-joomladay-germany

[Maxim Pishnyak]

And I can't see fatal error in your last post, Spike. Only fatal error could produce blank screen.

[Agaton]

Looks like a problem with one page checkout.  OPCs need updating for 2.0.22c/d - at least one 3rd party developer has released an updated version.

Thanks, I never gave that a thought. Just did that though same error messages.

VM templates are changed as of 2.0.22c  (not before) for security fixes.  http://virtuemart.net/news/list-all-news/446-important-security-release-vm-team-at-joomladay-germany

Did the templates only change in c/d, as the blank page issue has existed since 2.0.22b....

[Agaton]

And I can't see fatal error in your last post, Spike. Only fatal error could produce blank screen.

That's why I am bemused.... Something has fundamentally changed in VM for this to occur..... The danger is that if it is more common most people will revert back to the 2.0.22a version rather than look into it.

[Maxim Pishnyak]

You could try error reporting 'Simple' btw.