Topic-icon SCLogin may cause Virtuemart Registration page failure

Active Subscriptions:

None
4 years 4 months ago - 4 years 4 months ago #65854 by GlyCop
I was considering purchasing your SCLogin module, but I ran into a problem. It will not take my customers to my Virtuemart Registration page at glycop.com/index.php?option=com_virtuema...r&layout=editaddress for some reason. Instead, it takes people to this link with an error glycop.com/index.php?option=com_virtuemart&view=user

FIXED see RE: below...


If you get a blocked IP message while visiting glycop.com/ please let me know and I will adjust my firewall as well as give you access to my server in a private message.

I've tried nearly every setting including custom urls. Pictures are attached. I'm willing to pay for your time.

Here is a report produced by RuposTel.com at www.rupostel.com/utilities-for-joomla/ex...fatal-catcher-plugin.

This plg_system_fatal_catcher plugin detected a problem with your site. Your site caused a blank screen upon a visit of this URL: glycop.com:443/index.php?option=com_virtuemart&view=user

Error message data:
1 Call to a member function get() on null in file: /home4/glycopco/public_html/components/com_virtuemart/views/user/view.html.php line: 282

timestamp: 2019-11-30T07:25:28+00:00


To disable these emails proceed to your Extensions -> Plug-in manager -> disable plg_system_fatal_catcher
It is very important that you fix all php fatal errors on your site. Resend this email to your developer.

Backtrace:
/public_html/components/com_virtuemart/views/user/view.html.php:282
#0 /public_html/components/com_virtuemart/views/user/view.html.php(142): VirtuemartViewUser->shopper(Array)
#1 /public_html/components/com_virtuemart/controllers/user.php(59): VirtuemartViewUser->display()
#2 /public_html/libraries/src/MVC/Controller/BaseController.php(710): VirtueMartControllerUser->display()
#3 /public_html/components/com_virtuemart/virtuemart.php(120): Joomla\CMS\MVC\Controller\BaseController->execute('')
#4 /public_html/libraries/src/Component/ComponentHelper.php(402): require_once('/home4/glycopco...')
#5 /public_html/libraries/src/Component/ComponentHelper.php(377): Joomla\CMS\Component\ComponentHelper::executeComponent('/public_html...')
#6 /public_html/libraries/src/Application/SiteApplication.php(194): Joomla\CMS\Component\ComponentHelper::renderComponent('com_virtuemart')
#7 /public_html/libraries/src/Application/SiteApplication.php(233): Joomla\CMS\Application\SiteApplication->dispatch()
#8 /public_html/libraries/src/Application/CMSApplication.php(196): Joomla\CMS\Application\SiteApplication->doExecute()
#9 /public_html/index.php(49): Joomla\CMS\Application\CMSApplication->execute()
#10 {main}
Last edit: 4 years 4 months ago by GlyCop.
The topic has been locked.
Active Subscriptions:

None
4 years 4 months ago - 4 years 4 months ago #65855 by GlyCop
The SCLogin module may not be compatible with Joomla! 3.9.13 and Virtuemart 3.6.10 for some reason. Maybe these J&V versions are buggy? I will try and clone a test site at glycop.org/ if you want to get involved...?

I was able to correct the errors by rolling back my Joomla and Virtuemart version to...
Joomla! Version Joomla! 3.9.11 Stable [ Amani ] 13-August-2019 15:00 GMT
Joomla! Platform Version Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT
VirtueMart 3.6.8 10197
PHP Version 7.2.24

glycop.com/index.php?option=com_virtuemart&view=user displays just fine using SCLogin now that I rolled back J&V... I really like what you have built and hope to contribute by making a purchase as well as some constructive comments.

Sincerely,

Mike
Last edit: 4 years 4 months ago by GlyCop.
The topic has been locked.
Support Specialist
Mike,
That's really strange. There shouldn't be any incompatibilities with either of those versions, especially with such small version changes.

The big thing to look at is the URL that is created when it works versus when it doesn't. If they are different somehow or don't go to the correct page, then that would be the reason.. though the cause would still be unknown.

Either way, please keep us posted if you upgrade and and still run into issues. Obviously, we'd always recommend being on the latest versions, but I'd recommend upgrading one at a time and testing after each to help narrow down the potential culprit.

Thanks,
Alex
The topic has been locked.