Problem with SystemModule_Screen

[Kent Multer]

Hi folks,

I'm trying to use a system-ex module to force shoppers to a certain page under certain conditions. I did this by writing code SystemModule_Screen to detect the condition, and if it's present, to change the value of g.Screen. I'm pretty sure this used to work, but it's not working in this case. No matter what I put in g.Screen, the store ends up at the SFNT page.

Does anyone know what happened to this? I suspect its something related to new security features, or maybe URI management. I've been studying the LSK code for UI dispatching, but I don't see any obvious problems ... On the other hand, I can't even find the place where it actually renders the page, so apparently I'm having a bad day ... Hope someone can shed some light on this?

Thanks --

[dcarver]

What you described should work. The rendering of the page is done in merchant.mvc which isn't part of the LSK. The UI dispatch function attempts to determine and verify that the g.Screen code can be rendered under the current conditions. With that being said, I'm not seeing anywhere in that function where the page code is cleared out or being defaulted to "SFNT." The software will default to SFNT when the current value of g.Screen is blank. You should verify that you are correctly setting g.Screen in your system extension module.

[Bruce - PhosphorMedia]

sanity check: htaccess rules in play? possibly a URI management rewrite?

[Kent Multer]

Hi folks, David's hunch was correct. I left out some quotes in a couple of mvt:assign tags. So I was setting g.Screen equal to the contents of a variable named g.LOGN instead of to the actual value "LOGN."

Thanks for the help!