22
How can I cause XOOPS to set the cookie for the session to be .myhost.org instead of myhost.org?
I use mod_rewrite for a few modules and virtual hosts, for instance: forums.myhost.org is really myhost.org/modules/newbb/ but when the user logs in from myhost.org and the cookie is set from myhost.org then when accessing forums.myhost.org the session cookie is not sent because the domain names do not match.
By specifying .myhost.org, this will cause the browser to send the cookie to anything.myhost.org ... forums.myhost.org, myhost.org, whatever.myhost.org...
Can this be done?
CoolPops
Edit: I realized I posted this in the wrong forum. If a moderator sees this and would like to move it to, say, XOOPS general usage questions or a more appropriate forum I would appriciate that.
I use mod_rewrite for a few modules and virtual hosts, for instance: forums.myhost.org is really myhost.org/modules/newbb/ but when the user logs in from myhost.org and the cookie is set from myhost.org then when accessing forums.myhost.org the session cookie is not sent because the domain names do not match.
By specifying .myhost.org, this will cause the browser to send the cookie to anything.myhost.org ... forums.myhost.org, myhost.org, whatever.myhost.org...
Can this be done?
CoolPops
Edit: I realized I posted this in the wrong forum. If a moderator sees this and would like to move it to, say, XOOPS general usage questions or a more appropriate forum I would appriciate that.
23
Has anyone seen this problem before? I continue development but when I change a module template I must use the Update Module function to make the new template take effect. It's kinda getting tiresome. 
24
I'm not certian. It's a template change, maybe someone here can speak to the upgrade process when core templates have been changed.
If not, you may post another question (different subject) asking about the upgrade options when you change core module templates. You'll probably get a response that way.
I'm not certian what will happen because I have never done it myself so I have no experience in the upgrading when templates have change, sorry.
CoolPops
If not, you may post another question (different subject) asking about the upgrade options when you change core module templates. You'll probably get a response that way.
I'm not certian what will happen because I have never done it myself so I have no experience in the upgrading when templates have change, sorry.
CoolPops
25
You could probably just edit the template. My original thought would be to just but comments around the area you don't want, but that may cause undefined index problems.
What you should really do is (if you really want the stuff gone) is:
1. determine the names and default values for the items you wish to remove (view source on the editor should do that for you)
2. comment out the area you don't want
3. add in <input type="hidden" name="..." value="..."/>
That should do the trick. But watch out when you upgrade. Why don't you want them?
What you should really do is (if you really want the stuff gone) is:
1. determine the names and default values for the items you wish to remove (view source on the editor should do that for you)
2. comment out the area you don't want
3. add in <input type="hidden" name="..." value="..."/>
That should do the trick. But watch out when you upgrade. Why don't you want them?
26
I thought of that but it wouldn't make sense for the browser to then show the updated page as soon as I hit 'Update' in the module admin. To test this (ensure their's not something like that going on) I made a change to my template and viewed it in my normal browser (Firefox). No change. Hit refresh, Shift Refresh many times, no change. I then loaded Konqueror, logged in and hit Update on the module. Now back in Firefox, refresh... the changes appeared first time.
I went back, again, and double checked the setting:
"Update module template .html files from themes/your theme/templates directory?
If this option is enabled, module template .html files will be updated automatically if there are newer files under the themes/your theme/templates directory for the current theme. This should be turned off once the site goes public."
It indeed is set to yes. I even set it to No, hit go, then set it back to yes and hit go, still no go.
I went back, again, and double checked the setting:
"Update module template .html files from themes/your theme/templates directory?
If this option is enabled, module template .html files will be updated automatically if there are newer files under the themes/your theme/templates directory for the current theme. This should be turned off once the site goes public."
It indeed is set to yes. I even set it to No, hit go, then set it back to yes and hit go, still no go.
27
No cache enabled on any of my modules. I remember it working in the past and I didn't change anything with Xoops. But I edit my template and no change appears. If I refresh my module in the module manager then my changes appear.
29
During the development of my module I am making many, many edits to the templates and am finding that I have to go back and refresh the module each time to make my module template changes appear.
Is there a way to avoid this step? A setting I am missing somewhere or something?
Thanks,
CoolPops
Is there a way to avoid this step? A setting I am missing somewhere or something?
Thanks,
CoolPops
30
Whenever I use this control in a XoopsThemeForm I get the Calendar control information place before the start of the <html>. For some reason, Firefox is then redering a big padding around the whole site because of this error.
Has anyone else experienced this behavior?
Has anyone else experienced this behavior?
Login
Search
Recent Posts
Donat-O-Meter
| Stats | |
| Goal: | $15.00 |
| Due Date: | Oct 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $15.00 |
|
|