13
In the html/themes/yourTheme/blocks there are the templates for the blocks. And in the XOOPS admin/blocks are the templates for each block. CHeck also the css file, as there are colors and tr defined.
hope it helps
Markus
hope it helps
Markus
14
Hhhmmm.... I searched around, and have seen this tread:
https://xoops.org/modules/news/article.php?storyid=2602&page=2
This tread is from skalpa about XOOPS 2.3 / 2.4 and tells that this new releases (2.3/2.4) will be based on 2.0.13 and not 2.2.3. But a bunch of code "copied" from 2.2.3 "down" to 2.0.13.
=> This would mean I should use the 2.0.13 to start my mod dev. and grow with the 2.0.13 rel.
or will be so many code copied from 2.2.3 into 2.0.13 that it is more a 2.2.3 releas as a 2.0.13 release.
=> This means go with 2.2.3 as before recomandet already.
So I do not know which code base I should use now?
Or do I think to far and complicated? And just start and use the 2.2.3?
https://xoops.org/modules/news/article.php?storyid=2602&page=2
This tread is from skalpa about XOOPS 2.3 / 2.4 and tells that this new releases (2.3/2.4) will be based on 2.0.13 and not 2.2.3. But a bunch of code "copied" from 2.2.3 "down" to 2.0.13.
=> This would mean I should use the 2.0.13 to start my mod dev. and grow with the 2.0.13 rel.
or will be so many code copied from 2.2.3 into 2.0.13 that it is more a 2.2.3 releas as a 2.0.13 release.
=> This means go with 2.2.3 as before recomandet already.
So I do not know which code base I should use now?
Or do I think to far and complicated? And just start and use the 2.2.3?
15
2.2.3 is a good answer 
What are the reason for this decision?
with your example you mean:
$userid = !empty($xoopsUser) ? $xoopsUser->getVar('uid') : 0;
What are the reason for this decision?
with your example you mean:
$userid = !empty($xoopsUser) ? $xoopsUser->getVar('uid') : 0;
16
I think this is because the user did not acknowledge his account (second email). You can ack this user and then you should see the details.
I have this in the version 2.0.13.1 so hope it helps you
Markus
I have this in the version 2.0.13.1 so hope it helps you
Markus
17
If I start to develop a new XOOPS module.
=> Should I do it for 2.0.13.1 or 2.2.3?
In relation to:
- how easy to upgrade a module from 2.0.13.1 to next generation 2.xx?
- upgrade from 2.2.3 to the next generation version (based on 2.0.13.1)?
I do not wanna dev the module and as soon I'm finished I have to port it to another version.
Any other ideas, recomandation on this topic.
thx for any input
Markus
=> Should I do it for 2.0.13.1 or 2.2.3?
In relation to:
- how easy to upgrade a module from 2.0.13.1 to next generation 2.xx?
- upgrade from 2.2.3 to the next generation version (based on 2.0.13.1)?
I do not wanna dev the module and as soon I'm finished I have to port it to another version.
Any other ideas, recomandation on this topic.
thx for any input
Markus
18
As I know this has nothing to do with the mainfile.php.
You just have to update your apache configuration and your hosts file (if you have unix).
The host.domain.xy has to point to the right apache DocumentRoot and the same dir is configured in the mainfile.php. You can check this by just typing your ip address of your webserver and may with the dir /html/
hope it helps
Markus
You just have to update your apache configuration and your hosts file (if you have unix).
The host.domain.xy has to point to the right apache DocumentRoot and the same dir is configured in the mainfile.php. You can check this by just typing your ip address of your webserver and may with the dir /html/
hope it helps
Markus
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Dec 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|