I'll give it a try soon.
14
There has been a lot of effort on this subject, however:
- XOOPS 2.0.17 multixoops is not finished. I downloaded a version from http://sourceforge.net/projects/multixoops/ and I could not even make a clean install with it. The upgrade version did not work too.
- there is a module on simple-xoops.de that may create a multixoops, but I could not find a manual.
- the multix module (http://dev.xoops.org/modules/xfmod/project/showfiles.php?group_id=1359&release_id=1224#selected ) seems to be abandoned, in favor of the multixoops project. Although this seems to be the project that is closest to "a finished product" and although it has a good manual, I found it quite complicated and I did not get it to work.
- there has been the idea to install modules in the XOOPS_TRUST_PATH and to use this XOOPS_TRUST_PATH for shared modules. Never heard of recently.
- There is a hack in the FAQ: https://xoops.org/modules/smartfaq/faq.php?faqid=638
I probably have overlooked some great ideas. There have been a lot of ideas, but I don't believe that there is a finished product.
I need a live test site for one of my projects where I'll test a new theme. What I will probably do, is copy my files from example.com to testdomain.com . Then I'll adapt mainfile.php to the new patch info and I have a mirror site. In order to display another theme in each domain, I'll do this in my theme:
Let me know if this is a bad idea 8)
- XOOPS 2.0.17 multixoops is not finished. I downloaded a version from http://sourceforge.net/projects/multixoops/ and I could not even make a clean install with it. The upgrade version did not work too.
- there is a module on simple-xoops.de that may create a multixoops, but I could not find a manual.
- the multix module (http://dev.xoops.org/modules/xfmod/project/showfiles.php?group_id=1359&release_id=1224#selected ) seems to be abandoned, in favor of the multixoops project. Although this seems to be the project that is closest to "a finished product" and although it has a good manual, I found it quite complicated and I did not get it to work.
- there has been the idea to install modules in the XOOPS_TRUST_PATH and to use this XOOPS_TRUST_PATH for shared modules. Never heard of recently.
- There is a hack in the FAQ: https://xoops.org/modules/smartfaq/faq.php?faqid=638
I probably have overlooked some great ideas. There have been a lot of ideas, but I don't believe that there is a finished product.
I need a live test site for one of my projects where I'll test a new theme. What I will probably do, is copy my files from example.com to testdomain.com . Then I'll adapt mainfile.php to the new patch info and I have a mirror site. In order to display another theme in each domain, I'll do this in my theme:
le="color: #000000"><?php <{if $xoops_url=='http://www.testdomain.com'}> Here the theme for testdomain <{else}> Here the theme for my realdomain <{/if}>
Let me know if this is a bad idea 8)
15
Do you want to remove the copyright or do you want to remove the copyright notice on the public part of your site. I don't believe the latter is a problem, unless you use a piece of software other than the XOOPS core (module, theme or plugin) that is licensed in a way that this is forbidden.
Please note that the XOOPS core is licenced with the GNU GENERAL PUBLIC LICENSE Version 2, June 1991. Changing the license/copyright can only be done by the original author, other people are obliged to "share alike" the software if they distribute it... Changing the copyright is IMHO very, very difficult as it is a collaborative product (which is a good thing!).
_________________
Warning: the information above is provided 'as it is' and I accept no liability for any loss, injury or inconvenience sustained by any legal or natural person as a result of this information. Always verify critical information with the relevant authorities before you use it.
Please note that the XOOPS core is licenced with the GNU GENERAL PUBLIC LICENSE Version 2, June 1991. Changing the license/copyright can only be done by the original author, other people are obliged to "share alike" the software if they distribute it... Changing the copyright is IMHO very, very difficult as it is a collaborative product (which is a good thing!).
_________________
Warning: the information above is provided 'as it is' and I accept no liability for any loss, injury or inconvenience sustained by any legal or natural person as a result of this information. Always verify critical information with the relevant authorities before you use it.
17
I installed the OpenID module (https://xoops.org/modules/repository/singlefile.php?cid=59&lid=1733) on XOOPS 2.0.16 without problems.
However, when I log in with OpenID, I receive this error message:
Anyone?
However, when I log in with OpenID, I receive this error message:
le="color: #000000"><?php This page cannot be displayed due to an internal error. You can provide the following information to the administrators of this site to help them solve the problem: Error: No XML parser was found
Anyone?
18
Are you looking for something like this: https://xoops.org/modules/newbb/viewtopic.php?post_id=287443#forumpost287443 ???
19
Your theme is only for the lay-out.
You need to use a "block" called "New Members".
If you don't know what I am talking about, try to learn more about the difference between themes, templates, blocks and groups. You will need to know this if you work with XOOPS.
You need to use a "block" called "New Members".
If you don't know what I am talking about, try to learn more about the difference between themes, templates, blocks and groups. You will need to know this if you work with XOOPS.
20
I installed the module OpenID. When I try to login with an openid, it connects to the OpenID provider. Then it asks some info and when my browser is redirected to my site, I receive this error message:
(I don't know what info is safe to share, so I added a lot of xxxxxxx)
I followed the installation procedure according to the README file. As my server was in PHP safe mode, I manually made a folder called "_php_consumer" with its 3 subfolders (associations, nonces, temp) in the XOOPS Trust Path folder and I set the permissions to 777 (job done with FileZilla).
I also editted /modules/openid/library/Auth/OpenID/CryptUtil.php changing
in
XOOPS version = XOOPS 2.0.16
Any ideas how to get it working??
le="color: #000000"><?php msg: OpenID authentication failed: 'return_to' not signed Array ( [janrain_nonce] => 2008-07-24xxxxxxx [openid1_claimed_id] => xxxxxxxxxxxxxx [openid_sig] => xxxxxxxx [openid_mode] => id_res [openid_return_to] => xxxxxxxxxxx [openid_identity] => xxxxxxxxxxx [openid_signed] => identity%2Creturn_to%2Cmode [openid_assoc_handle] => xxxxxxxxxxxx [__utma] => xxxxxxxxxxxxxx [__utmz] => xxxxxxxxxxxxxxx [art_438] => xxxxxxx [art_78] => xxxxxxx [art_430] => xxxxxxx [editor] => tinyeditor [art_441] => xxxxxxx [art_412] => xxxxxxx [art_402] => xxxxxxx [art_82] => xxxxxxx [session] => xxxxxxx [PHPSESSID] => xxxxxxx [__utmb] => xxxxxxx [__utmc] => xxxxxxx [art_18] => xxxxxxx [xoops_session] => xxxxxxx )
(I don't know what info is safe to share, so I added a lot of xxxxxxx)
I followed the installation procedure according to the README file. As my server was in PHP safe mode, I manually made a folder called "_php_consumer" with its 3 subfolders (associations, nonces, temp) in the XOOPS Trust Path folder and I set the permissions to 777 (job done with FileZilla).
I also editted /modules/openid/library/Auth/OpenID/CryptUtil.php changing
le="color: #000000"><?php define('Auth_OpenID_RAND_SOURCE', '/dev/urandom');
in
le="color: #000000"><?php define('Auth_OpenID_RAND_SOURCE', null);
XOOPS version = XOOPS 2.0.16
Any ideas how to get it working??
Login
Search
Recent Posts
Donat-O-Meter
| Stats | |
| Goal: | $15.00 |
| Due Date: | Aug 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $15.00 |
|
|