883
The easist way to do this for each client is to add a little javascript into your theme. Something like:
This will display today's date in a format like
<script type="text/javascript">
<!--
var currentTime = new Date()
var month = currentTime.getMonth() + 1
var day = currentTime.getDate()
var year = currentTime.getFullYear()
document.write(month + "/" + day + "/" + year)
//-->
</script>
This will display today's date in a format like
8/19/2006
886
Here's what I think I'd do as a start:
1) Upgrade to 2.0.14. There were some security fixes in addition to other things.
2) Check directory and file rights to make sure they're what they should be.
3) Check the users in the database to make sure there isn't a user with administrator rights that you aren't expecting.
4) Check the forums for information on the modules you have installed to see if there are vulnerabilities that have been identified. You might want to post the modules you use here (along with their versions) so the community can help you do some of the research.
5) Check your web logs to see if you can see where the attack came from and ban the IP.
6) Contact your web host to see if they can help you identify how the attack occurred (to make sure it wasn't through the server instead of through Xoops).
1) Upgrade to 2.0.14. There were some security fixes in addition to other things.
2) Check directory and file rights to make sure they're what they should be.
3) Check the users in the database to make sure there isn't a user with administrator rights that you aren't expecting.
4) Check the forums for information on the modules you have installed to see if there are vulnerabilities that have been identified. You might want to post the modules you use here (along with their versions) so the community can help you do some of the research.
5) Check your web logs to see if you can see where the attack came from and ban the IP.
6) Contact your web host to see if they can help you identify how the attack occurred (to make sure it wasn't through the server instead of through Xoops).
887
Since it was just a test install, and assuming you don't want to keep any of the data you have entere into the Tiny Content module - I would just uninstall the module and then reinstall it.
888
Let me start by saying I haven't used this module - but I do have a suggestion based on other modules I've used.
I assume you're entering when you're entering the address. Have you tried entering instead? Some modules evaluate the contents of the field and if it doesn't start with "http://" assume it's a relative link inside your site and add the XOOPS_URL to the contents typed in the field....
Just a thought.
I assume you're entering
www.townloafer.com
http://www.townloafer.com
Just a thought.
889
Now that I think about it you will probably have to uninstall the module and then re-install it to get it to work using the /sql/mysql.sql file - if you do this you will lose the data for this module.
In order to do this without uninstalling the module you'll have to use phpMyAdmin (or similar) and perform an SQL statement on the table...
WARNING: BACKUP YOUR DATABASE BEFORE YOU ATTEMPT THE FOLLOWING. YOU COULD SERIOUSLY 'DAMAGE' YOUR DATABASE IF YOU DO NOT DO THIS CORRECTLY.
Now, with the warning out of the way - to do this without uninstalling your module you'll need to go to phpMyAdmin and then select the table. Then Select the SQL tab and type the following:
ALTER TABLE xoops_catads_ads MODIFY view INT UNSIGNED NOT NULL
NOTE: The table name prefix (xoops_ in the statement above) will be different depending on the particular XOOPS installation.
In order to do this without uninstalling the module you'll have to use phpMyAdmin (or similar) and perform an SQL statement on the table...
WARNING: BACKUP YOUR DATABASE BEFORE YOU ATTEMPT THE FOLLOWING. YOU COULD SERIOUSLY 'DAMAGE' YOUR DATABASE IF YOU DO NOT DO THIS CORRECTLY.
Now, with the warning out of the way - to do this without uninstalling your module you'll need to go to phpMyAdmin and then select the table. Then Select the SQL tab and type the following:
ALTER TABLE xoops_catads_ads MODIFY view INT UNSIGNED NOT NULL
NOTE: The table name prefix (xoops_ in the statement above) will be different depending on the particular XOOPS installation.
890
NOTE: I haven't tried this on an installed catads module but it SHOULD work.
==========================================================
If you edit line 33 in the /sql/mysql.sql file it will fix this for you. The easy change below will show up to 255 views instead of 127. If you want more than that then you'll need to change the declaration from a 'tinyint' to an 'int'....
Change line 33 from:
`view` tinyint(2) NOT NULL default '0',
to:
`view` tinyint(2) UNSIGNED NOT NULL default '0',
After you make this change go to Admin > Modules and update the module.
==========================================================
If you edit line 33 in the /sql/mysql.sql file it will fix this for you. The easy change below will show up to 255 views instead of 127. If you want more than that then you'll need to change the declaration from a 'tinyint' to an 'int'....
Change line 33 from:
`view` tinyint(2) NOT NULL default '0',
to:
`view` tinyint(2) UNSIGNED NOT NULL default '0',
After you make this change go to Admin > Modules and update the module.
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | May 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|