2
I'm the same... with all of these hacks, I see text boxes instead of images.
My process to install:
1. Delete original xoopspoll directory (start fresh).
2. Upload new xoopspoll directory from hack archive.
3. Update the module from the admin interface.
4. Re-generate template (in one case: xoopspoll_block_results.html).
5. Clear templates_c.
Why on earth would text boxes appear? Something I'm missing here?
Edit: it seems to be using xoops_block_poll.html when it should be using xoops_block_results.html?
Edit2: the above shot was taken while the site had jayjay's version installed.
My process to install:
1. Delete original xoopspoll directory (start fresh).
2. Upload new xoopspoll directory from hack archive.
3. Update the module from the admin interface.
4. Re-generate template (in one case: xoopspoll_block_results.html).
5. Clear templates_c.
Why on earth would text boxes appear? Something I'm missing here?
Edit: it seems to be using xoops_block_poll.html when it should be using xoops_block_results.html?
Edit2: the above shot was taken while the site had jayjay's version installed.
3
Aha! Thank you 
Believe it or not, I did search fairly carefully through the forums but must've used the wrong keywords.
Believe it or not, I did search fairly carefully through the forums but must've used the wrong keywords.
4
Yeah, we know about the PHPBB module but we'd like to stick with NewBB if at all possible because it seems well-integrated into XOOPS itself. Also because every man and his dog out there has a PHPBB-based forum 
5
We wanted to make some adjustments to the look of our NewBB forums, particularly oursite.com/modules/newbb/viewforum.php?whatever... So I made some subtle markup changes to modules/newbb/templates/newbb_viewforum.html. Upload, hit F5. Nothing, no change.
Right, sez I, it's cached somewhere. I emptied out templates_c and hit reload. Still nothing.
What am I missing here? Am I even editing the right file?
Right, sez I, it's cached somewhere. I emptied out templates_c and hit reload. Still nothing.
What am I missing here? Am I even editing the right file?
6
I wonder if anyone could post an update on the status of NewBB2, what still needs to be done, and if there are tasks that can be farmed out to the XOOPS community. I know I'd be happy to help in order to speed up the process of getting this promising new version out the door and into the hands of users.
7
Quote:
Well, I don't think that's entirely true. There is obviously something about the way XOOPS does sessions that, on certain servers, causes problems. If there wasn't, it wouldn't have happened on our site as well!
Just because it doesn't happen to everyone doesn't mean it's not a bug. We just have to figure out why it happens, and how to get rid of it.
Now, for us the solution was to turn custom session handling off. At least, no-one has reported the problem since then! So what is it about custom session handling that could cause this, and what are the common factors in the servers that have exhibited the problem? That's the line of questioning we should follow. I don't think it's terribly helpful to suggest that the original poster is at fault because it couldn't possibly be XOOPS
BTW, we modified no core XOOPS files.
Oh, and if you wanted to see 'undue alarm' you should've seen the other site admin and myself on Sunday night when we discovered the security problem, about an hour after the site went live!
DobePhat wrote:
this thread doesnt make sense and is causing undue alarm.
You ar insinuating its XOOPS. It's not.
Well, I don't think that's entirely true. There is obviously something about the way XOOPS does sessions that, on certain servers, causes problems. If there wasn't, it wouldn't have happened on our site as well!
Just because it doesn't happen to everyone doesn't mean it's not a bug. We just have to figure out why it happens, and how to get rid of it.
Now, for us the solution was to turn custom session handling off. At least, no-one has reported the problem since then! So what is it about custom session handling that could cause this, and what are the common factors in the servers that have exhibited the problem? That's the line of questioning we should follow. I don't think it's terribly helpful to suggest that the original poster is at fault because it couldn't possibly be XOOPS
BTW, we modified no core XOOPS files.
Oh, and if you wanted to see 'undue alarm' you should've seen the other site admin and myself on Sunday night when we discovered the security problem, about an hour after the site went live!
8
If a developer would like to look at our site, I think we would be willing to provide admin level access to it. PM me, I'll keep checking this thread and PM's.
9
Ok, we turned off custom session handling and the user who reported being logged in as somebody else was no longer able to do so.
???
Scary.
???
Scary.
10
We are now experiencing what sounds like exactly the same problem. Visitors go to the site and find they are already logged on as somebody. Obviously this is a serious (and not isolated) security issue!
We're running v2.0.7.
We're running v2.0.7.
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Apr 30 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|