2
Thanks ghia that got it working when submiting a ad but not when a user clicks the email seller link was hoping to put it in that form as well .
3
Trying to work out how to add captcha to Catads submit adds and contact forms .There is mention of security image in index php but i cannot work out the rest .
4
Trying to install TinyMCE in a test site with 2.0.18.1 and im getting this error below when trying to edit new article there no editor showing on the page just wondering if there is a fix or something i may have over looked .
Quote:
Quote:
Warning: fgets(): supplied argument is not a valid stream resource in file /modules/tinyeditor/include/initcode.php line 227Warning:
fclose(): supplied argument is not a valid stream resource in file /modules/tinyeditor/include/initcode.php line 231
5
I have just installed Mastop Publish to a site running 2. and do not seem to be able to give guest user actcess to the module. Always seem get ( dont have permission to enter ).
Also now i seem to be getting ( Valid token expired ) And cannot alter any permisions
Also now i seem to be getting ( Valid token expired ) And cannot alter any permisions
6
I would like to ad to the list of Marco's
I use some steps as you probably do when I test/debug modules. It's a quick contribution to our smoketest methodology :
Light explanation :
0/ Validate xoops_version file
>> 0a/ Instalation Help / Readme are included etc
1a/ Test module installation
1b/ Test module upgrade (refresh in admin)
1c/ Test update script (i.e no data are lost)
2/ Play with module under debug mode
- Test admin configuration
>> with a scale of user usability eg: 1=Easy 2 =Medium 3=Hard
- Test use of smarty variables
- Test bloc configuration
3/ Validate translation directories
it's a quick list, I know, but it's the "methodology" I usually use... I'm shure you make other/better tests too !
4/ >> Test user interface ( with various Browsers operating systems )
>> XHTML 1.0 Transitional template output
----------------------------------------------------
Couple Question for the Module Developers
1 ) Has there been any decision made on the developer side of the CSS issue of each module having seperate Css files which means when " a basic normal user " adds a module they then have to try and find the right file to edit to get colour right .
( my 1 cents worth )
Themes and modules sort of run hand in hand in my mind so realy the impact on themes should be part of the QA .
Maybe we should use a number of standard themes wether they are the ones bundeled with XOOPS package or what the Theme Forge say are up to stardard . Then the resuls incorperated in the certification that the module compatible with X theme's .
With a scale (1)= Compatable (2)= Possible Minor Template or CSS Modification Needed .
Cheers
Peter
I use some steps as you probably do when I test/debug modules. It's a quick contribution to our smoketest methodology :
Light explanation :
0/ Validate xoops_version file
>> 0a/ Instalation Help / Readme are included etc
1a/ Test module installation
1b/ Test module upgrade (refresh in admin)
1c/ Test update script (i.e no data are lost)
2/ Play with module under debug mode
- Test admin configuration
>> with a scale of user usability eg: 1=Easy 2 =Medium 3=Hard
- Test use of smarty variables
- Test bloc configuration
3/ Validate translation directories
it's a quick list, I know, but it's the "methodology" I usually use... I'm shure you make other/better tests too !
4/ >> Test user interface ( with various Browsers operating systems )
>> XHTML 1.0 Transitional template output
----------------------------------------------------
Couple Question for the Module Developers
1 ) Has there been any decision made on the developer side of the CSS issue of each module having seperate Css files which means when " a basic normal user " adds a module they then have to try and find the right file to edit to get colour right .
( my 1 cents worth )
Themes and modules sort of run hand in hand in my mind so realy the impact on themes should be part of the QA .
Maybe we should use a number of standard themes wether they are the ones bundeled with XOOPS package or what the Theme Forge say are up to stardard . Then the resuls incorperated in the certification that the module compatible with X theme's .
With a scale (1)= Compatable (2)= Possible Minor Template or CSS Modification Needed .
CheersPeter
7
Dont quote me on this but Fantastico will note install your XOOPS site in the root directory eg : www.jensclassroom.com/ but will install it in a subfolder eg XOOPS or what ever you name it .
my guess DOMAININSTALLDIR should be the directory
my guess DOMAININSTALLDIR should be the directory
8
This link below should help we that Question Dennis
https://xoops.org/modules/newbb/viewtopic.php?topic_id=24061&forum=7
https://xoops.org/modules/newbb/viewtopic.php?topic_id=24061&forum=7
9
You could use the Squirrel Mail Module has a few bugs/glitchs but works ok i have found .
Um also you could install the webmail program in seperate direcory and use a iframe module to wrap it in your XOOPS site .
Um also you could install the webmail program in seperate direcory and use a iframe module to wrap it in your XOOPS site .
10
Hopefully this might help
go into your theme.html
find
add a class instead of background color
then add the class to the style.css file
should work
well it seems to in " phpkaox" theme on my test sever
go into your theme.html
find
<table cellspacing="0"><tr>
<td width="whatever" background="whatever">
<!-- Start left blocks loop -->
<{foreach item=block from=$xoops_lblocks}>
<{include file="/theme_blockleft.html"}>
<{/foreach}>
<!-- End left blocks loop -->
add a class instead of background color
<table cellspacing="0"><tr>
<td width="whatever" class="b1">
<!-- Start left blocks loop -->
<{foreach item=block from=$xoops_lblocks}>
<{include file="/theme_blockleft.html"}>
<{/foreach}>
then add the class to the style.css file
.b1 { background-image:url('images/b1.jpg');
should work
well it seems to in " phpkaox" theme on my test sever
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 |
 |
|