W0000H0000!!!!

this was a lot easier than i thought

find file: kernel/session.php line ~117

add the line after open brace


you do NOT need to add stripslashes() in the reader

now it's time for sleep

the fix has been reported in the bugs forum.

i like Xoopy ROAR!

after doing some more digging, i think i might have found it. XOOPS IS probably doing something to my single quotes because it gets sent to the database.

i'll post again when/if i can fix it (unless it really was my prog, but now doubt that is the case)

[edit]
Now i'm 100% certain that it's XOOPS that is causing the problem. after commenting out the module started working fine with single-quotes. now to figure out the fix.
*pulls more hair out*

The FIX 2 posts down has been reported in the bugs forum.

I'm having one hell of a time debugging a module. whenever i serialize an object that has single quote (') attributes, the object either gets array(), unset, or never saves the info.

having tested the object right after serializing it to the session shows the single-quotes are still there, but after it finishes loading the page to be used again (it sends a header('page.php');die(); right after serializing), the error pops up.

does XOOPS perform some kind of security check on all objects in the session? i'm pretty sure it's somewhere hidden deep in my code (it's a port from a stand-alone smarty app) but thought i'd give it a shot to see if it was really XOOPS doing something so i can stop pulling my hair out.

thanks all :)

fwiw, i'm saving it like

btw, it works fine if the user doesn't type in a single-quote and works fine on the pre-xoops site (with or without single-quotes).

i meant, is there an easy way to do it like in the module (user side)? i've looked though a lot of other modules and their admin side files all mix php with html than just using smarty.

my point was when/if the admin-side will be using smarty by default. afaik, i have to start including every smarty piece than letting the XOOPS core do it for me.

ex:

gives me an error


[edit]
Wow. that was easier than i thought; didn't know i can still call the 'db:' argument in the $xoopsTpl->display. for anyone else that's interested, this is all you need in the admin file

^bump

I like the holiday banner. looks really spiffy and reminds me of something i'd see on TechTV

Happy Holidays everyone

I doubt this is possible, but i'll try anyways.

Can i put in variables inside the define() like in language/english/main.php? What i want to do is make error messages along with the user's input. by doing this, the user sees exactly what s/he typed in.

ex: i have an error check for duplicate titles and want to use redirect_header() saying something like "Sorry, title <b>How old are you? is already in use. <br />Sending you back to the editor".

[edit]
hmm.. how about this work-around: split the language files, so redirect_header() will look like


Is this how everyone else does it?

i'm with RicoCali on this one. there are a lot of sites that do this such ashttp://xbox-scene.com (just for example, doubt they use xoops). users will get the same info in the small right or left block as they do with a full-page center block.

Admin Side
1. More user-friendly interface.
When adding several new category or forum, it's a pain in the butt because i get sent back to newBB's main menu which means a lot of clicking. phpBB's interface is pretty good since you see everything in one window and the ability to add categories, forums, and re-arrange right there. In addition to that, we see the category each forum belongs to. As it is now, if we have an "Announcements" forum in every category, how do we know which "Announcements" we are editing if we want to change the title? (We just have a dropdown with several "Announcements" forums).

2. unlimited sub categories

3. Moderator is optional. If no moderator is assigned, the Admin is the implied moderator.

4. Remember our input if you must display an error on a seperate page. i dont remember how many times i forgot to put something in after typing out a long-ish description. now i save everything to notepad before hitting submit.

User Side
links in each post (suggested placement)
1. Link going to recipient (who post was for)
- Right-alined on the "Posted on" bar
- <a href...>@Post#3</a>
2. Link for that specific post (for easy reference linkage)
- Before poster's name
- Probably post #in thread (ie: 3rd post has an <a href...>post3</a>
3. (bug?) When we post in a multi-page thread, we get sent to the first page than our post.
4. Highlight searched text ala vB
- &highlight=text+query in the url will highlight all matching text in the thread
5. show only one instance for each thread hit (in searches)
6. show search results by post
7. search query must be in body of a post, not the whole thread.
ie: "cookie AND disabled ie OR mozilla"
because of the quotes, and AND/OR constraints, every query must be in someone's post. if cookie and disabled appeared in sperate posts, it will not be a successful hit.
8. (NEW) numbered, bulleted listing (with sub-sub-sub bullets)
maybe something like
[list]
[*]main cat1
[*][*]sub cat
[*][*][*]sub sub cat
[*]main cat2
[/list]
don't know of any boards that allow this (sub cats)
9. (NEW) Tables? similar to Smarty's wiki
||cell one || cell two ||
|||| big ol' line ||
|| cell four || cell five ||
(notice empty cell in row two)
i don't think any other message board allows tables
10. google-like searches cookie -mozilla
11. [php][/php]
12. highlight a word, click the link button, type url, and presto the word is now surrounded by [url=http://..]word[/url]
13. allow registered users to specify how many posts per page we can vew (ie: 20, 50, 100, 200 posts per thread page). same with thread listing
14. prune to tar.gz (so we still have a history)
15. auto-check "notify me.." when submitting or replying to a thread. it should see our preference via our account settings. (send notification by email)