62
Hi!
These days I have more ideas than time to develop them, but I've been thinking this: It would be terribly useful to be able to audit XOOPS DB activity. Having this, you would be able to recover an old version of an article, check who modified what, etc.
The idea is:
· Store all INSERT and UPDATE queries in a table, accompanied by User ID and Date.
· Create an admin interface to navigate and search through all these operations.
The problem is that I want to find the cleanest way to do it, andI don't find any way to do it without modifying the DB class file. I don't know for sure, but I think PHP as nothing like Javascript listeners.
Suggestions? Ideas?
These days I have more ideas than time to develop them, but I've been thinking this: It would be terribly useful to be able to audit XOOPS DB activity. Having this, you would be able to recover an old version of an article, check who modified what, etc.
The idea is:
· Store all INSERT and UPDATE queries in a table, accompanied by User ID and Date.
· Create an admin interface to navigate and search through all these operations.
The problem is that I want to find the cleanest way to do it, andI don't find any way to do it without modifying the DB class file. I don't know for sure, but I think PHP as nothing like Javascript listeners.
Suggestions? Ideas?
63
Sorry, I'd need to see the template, and I'm gonna disconnect now and won't be back online till monday.
If you can wait, I'm sure it has a very easy solution. Paste here the template, if it's not me, sure someone will be able to help you.
But so to say, if you're using the code you pasted in a earlier post, this tag...
<{$story.imglink}>
Is the problem. This tag contains the IMAGE + the link, a bad idea some XOOPS coder have from time to time. A tag should never contain two items, no matter what they are, link and image should be separated.
Look in the smarty console for a tag that contains only the image, and another one that only contains the link to the article, then edit your template, so
<{$story.imglink}>
becomes
<a href="Link to the article"><{$story.image}></a>
If you don't find any tag that contains only the image, you'll have to go yourself into the code, locate where is <{$story.imglink}> generated (look for "imglink" in the source), then add or modify the code to generate the tag you need.
Good luck.
If you can wait, I'm sure it has a very easy solution. Paste here the template, if it's not me, sure someone will be able to help you.
But so to say, if you're using the code you pasted in a earlier post, this tag...
<{$story.imglink}>
Is the problem. This tag contains the IMAGE + the link, a bad idea some XOOPS coder have from time to time. A tag should never contain two items, no matter what they are, link and image should be separated.
Look in the smarty console for a tag that contains only the image, and another one that only contains the link to the article, then edit your template, so
<{$story.imglink}>
becomes
<a href="Link to the article"><{$story.image}></a>
If you don't find any tag that contains only the image, you'll have to go yourself into the code, locate where is <{$story.imglink}> generated (look for "imglink" in the source), then add or modify the code to generate the tag you need.
Good luck.
65
Great news, great news.
As usual, I'll wait for the EXM edition of every new release until the old control panel is replaced. I hope it happens soon!
As usual, I'll wait for the EXM edition of every new release until the old control panel is replaced. I hope it happens soon!
66
I use a search module developed by
Dan Musil and Jirka Vrba (http://www.qcm.cz)
It's just a modularized copy of the search engine, modified to use Smarty templates (oh, yes!), so you can tune looking and working without modyfing the core.
It's old, but still recommended. I think it' a good starting point for anyone that wants to improve the search engine. Instead of hacking the core, you just work on a module that can be removed at any time.
NOTICE: old version had a bug. I send them the fix, but don't know if they released a new version with the fix.
Dan Musil and Jirka Vrba (http://www.qcm.cz)
It's just a modularized copy of the search engine, modified to use Smarty templates (oh, yes!), so you can tune looking and working without modyfing the core.
It's old, but still recommended. I think it' a good starting point for anyone that wants to improve the search engine. Instead of hacking the core, you just work on a module that can be removed at any time.
NOTICE: old version had a bug. I send them the fix, but don't know if they released a new version with the fix.
68
FOrget it, I found a solution. When calling jQuery, don't use $, but simply "jQuery" like this:
jQuery(document).ready();
The problem is that XOOPS own javascript defines a function named $, just like jQuery. One overwrites the other.
jQuery(document).ready();
The problem is that XOOPS own javascript defines a function named $, just like jQuery. One overwrites the other.
69
FOrget it, I found a solution. When calling jQuery, don't use $, but simply, jQuery, like this:
jQuery(document).ready();
jQuery(document).ready();
70
Hi!
What is $ function used for in XOOPS? This function makes JQuery incompatible. WHat's it for, and more importent, what files do they use it? I need to replace all $ calls by any other thing to use jQuery...
...and of course a search & replace for $ is not a good idea.
What is $ function used for in XOOPS? This function makes JQuery incompatible. WHat's it for, and more importent, what files do they use it? I need to replace all $ calls by any other thing to use jQuery...
...and of course a search & replace for $ is not a good idea.
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 |
 |
|