Dumb question: Where are the template variables stored?

Well...i'm not worried what others do. Its their business. I was only very much appreciated for someone to give me advice. For me, I always stay legal and buy the software license if it is of value to me and I'm using it professionally. I think in the agreement to use XOOPS site is that you are responsible for your own posting.

thank you very much for the link tried it out and went ahead and registered a license. I hear these guys are cracking down on licenses.

Can anyone recommend a good CSS editor with preview?

I agree and I think "homehome" is a typo also. I think it should be:

ln -s /var/html/www /home/hogehoge/xoops


These lines are also incorrect...

define("XOOPS_THEME_URL", "http://www.hogehoge.com/themes");
define("XOOPS_UPLOAD_URL", "http://www.hogehoge.com/uploads");

It should be:

define("XOOPS_THEME_URL", "http://www.hogehoge.com/public_html/themes");
define("XOOPS_UPLOAD_URL", "http://www.hogehoge.com/public_html/uploads");

I hope ONO clears this up...

The only thing missing with the solution is the database end and the modules. The installer sets up the database and creates the initial tables. Can we run installer with this implementation to do that?

Also, I don't think he is refering to mainfile.php to put in these modifications. Isn't he referring to common.php instead. XOOPS_CACHE_PATH, XOOPS_UPLOAD_PATH, XOOPS_THEME_PATH", XOOPS_COMPILE_PATH, XOOPS_THEME_URL and XOOPS_UPLOAD_URL are all in common.php not mainfile.php. If so, then we should write a wrapper for common.php instead of mainfile.php. I'm real confuse with these instructions.

...anyone?

I would like to thank ONO for providing this codebase example for us...as it is great value to me. Unfortuneately, there are some typo errors in his follow example and need someone to verify. I'm a bit confused with the directory paths that he has used. I think they are typos. Also the softlink looks wrong also. "homehome"?:


This should be now a lot easier in 2.0.4.

Let's say that you have uploaded all XOOPS files to /var/html/www, and want all other users to share these files.

First, for each of the virtual domains, create mainfile.php in which following constants are defined:
XOOPS_CACHE_PATH, XOOPS_UPLOAD_PATH, XOOPS_THEME_PATH", XOOPS_COMPILE_PATH, XOOPS_THEME_URL, XOOPS_UPLOAD_URL

For example, mainfile.php of 'hogehoge' user will be something like below:

define("XOOPS_CACHE_PATH", "/home/hogehoge/xoops/cache");
define("XOOPS_UPLOAD_PATH", "/home/hogehoge/public_html/uploads");
define("XOOPS_THEME_PATH", "/home/hogehoge/public_html/themes");
define("XOOPS_COMPILE_PATH", "/home/hogehoge/xoops/templates_c");
define("XOOPS_URL", "http://www.hogehoge.com/xoops");
define("XOOPS_THEME_URL", "http://www.hogehoge.com/themes");
define("XOOPS_UPLOAD_URL", "http://www.hogehoge.com/uploads");
define('XOOPS_DB_PREFIX', 'xoops');
define('XOOPS_DB_USER', 'hogehoge_xoops');
define('XOOPS_DB_PASS', 'hogehoge');
define('XOOPS_DB_NAME', 'hogehoge_xoops');

and the directory structure of the user will be like below:

/home/hogehoge/xoops/mainfile.php
/home/hogehoge/xoops/cache/ (chmod 777)
/home/hogehoge/xoops/templates_c/ (chmod 777)
/home/hogehoge/public_html/uploads/ (chmod 777)
/home/hogehoge/public_html/themes/

Next, create symlink between the user directory and the directory where XOOPS core files are uploaded

ln -s /var/html/www /home/homehome/public_html/xoops

The final step is to modify the /var/html/www/mainfile.php file so that it will read mainfile.php placed under the user directory. If you are running Apache you can use $_SERVER['DOCUMENT_ROOT'] to get the directory of the user.

But that is already done. When you redirect to the page with the graphical result...(10% yes 90% no) all that information is already there. Just post it on the block instead of a separate page.

Quote:

Gracias Sergio..

Quote:

It is possible...you guys are the best! But I see that this makes sense. Why can't you display the graphical result on the block? I see other polls do it.

Thank you for listening...