Defaulting to Application page instead of blank page?

[jegelstaff]

@tikyon reports...

"I notice that you have changed how the landing page is rendered when “Formulize” is selected for the user group. In my projects, we currently utilize the menu items that displays on /modules/formulize/application.php?id=all after logging in. I was wondering if you have any suggestion for retaining the same behaviour other than manually editing index.php to skip the if-block at line 39."

This is a little funny... I think all you have to do to get the behaviour you want is to modify the IF condition at line 44 in the index.php:

if(!$startFid AND !$startSid AND !$startURL) {

Becomes:

if(!$xoopsUser AND !$startFid AND !$startSid AND !$startURL) {

I believe, but I'm not certain, that the issue is when anon users with no Formulize start page are shunted to Formulize, they may very well get a completely blank page, and the login page may be hidden/unavailable depending on the theme, or at least it would be offscreen and they would be sort of trapped, or really trapped, with no way to login.

So we nullified the startpage so that login would always be possible because people would remain on the front page.

But I think that was just done because of the pathways for anons, and for regular users already logged in, then this is not a problem. So if you keep them with a Formulize start page, then the Formulize behaviour would kick in when they are shunted to the page, and the application.php page is the default when the user does not have a default page specified through the Menu system.

Let me know if this modification suits your needs and resolves the problem, and we'll look at including it in the next release.

--Julian

[tikyon]

Your suggestion works! It's now landing the same way as before.

[jegelstaff]

Fixed in https://github.com/jegelstaff/formulize/commit/f3386602c061867bae04493b74a5d5cf8ae055d8 and https://github.com/jegelstaff/formulize/commit/cf2cdbb5dde4bb1b177ce2eaeebc6bd26ac13770