| Re: Making single pages of a module public |
| by brash on 2004/7/7 0:40:26 Nice work Groover, I'll be interested to see the end product. |
| Re: Making single pages of a module public |
| by Groover on 2004/7/6 20:52:19 Actually if you comment out all that code then if a user is logged in, that page will appear as if they are not. If you instead comment out from: if ($xoopsConfig['closesite'] == 1) { to the second to last closing brace (inclusive) then the page will appear correctly for both logged in and not logged in. Groover |
| Re: Making single pages of a module public |
| by Groover on 2004/7/6 20:40:43 Thanks! That appears to work just fine! I copied common.php into my module folder and renamed to commonpublic.php. Included in my .php file for my public web page. Set tbe nocommon option. Then commented out everything from: ############## Login a user with a valid session ############## to the second-to-last closing brace. Seems to work with no side effects. Cheers!  Groover |
| Re: Making single pages of a module public |
| by Dave_L on 2004/7/6 20:18:56 I did something similar. My solution was to set $xoopsOption['nocommon'] = 1 before including mainfile.php, and then include a stripped-down copy of include/common.php without the web-related or permissions-related code. |
| Re: Making single pages of a module public |
| by Groover on 2004/7/6 19:38:56 I guess it isn't possible then?  Groover |
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $15.00 |
| Due Date: | Jul 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $15.00 |
|
|