Quote:

MadFish hit the nail on the head. No matter what you do to build a revenue stream on your site, you have to be able to draw people to the site. The key element here is to figure out what value your site adds to your customer.

Portals -- XOOPS is a portal-builder after all -- offer value through a confluence of content, community and commerce. If you are providing content of value then you need to make sure that you are delivery content that is of good quality and that is updated frequently. If part of your model is the community that forms around your site then you need to make sure that community is actively engaged. And don't forget the opportunity to engage in commerce. Your business may not look like an e-commerce shop, but there are always opportunity to sell goods and services to your customers. Subscription models for premium content depend on...well... premium content.

Regardless of the focus of your site, you need to be actively marketing it. People who aren't customers now need to know that they can be customers. And that involves, as was mentioned above, posting actively in message boards and groups that relate to topics of interest to your customers. If you know who they are and what problems they are trying to solve then you should be able to find the places that they frequent and get your message across.

Why two sites?

A single logon with two different classes of users (members and rush candidates) would give you the ability to share logons and content across the two user populations. Members would see member content plus shared content and candidates would see candidate content plus shared content.

There are a lot of possibilities here. What exactly are you trying to accomplish?

james

You may be seeing the result of a problem passing the HTTP_REFERRER information. Take a look here: Why after login am I still denied access?

There is a tutorial on using PHP with Tomcat over on the Apache site. You can find it here: http://wiki.apache.org/jakarta-tomcat/UsingPhp.

I've never tried this, but it looks like they are having you build the phpsrvlt.jar and libphp4.so that MadFish was mentioning.

Good luck.

James

I just upgraded to 2.2.1 and that fixed the problem.

Unfortunately, the slashes don't show up in the Admin page. I've even tried deleting the block and recreating it. Whenever I have a single quote in the text, there are backslashes and single quotes in the display.

Thanks for the suggestion though.

I've just upgraded to XOOPS 2.2, and I'm having trouble with slashes in a custom block.

I have a simple block that displays some welcome text. But the text has slashes before every apostrophe -- single-quote. My best guess here is that the text is not being stripslashed after it is read. The slashes are in the database fields, but they aren't being stripped out before display.

Has anybody else seen this?

Thanks

James

Thanks stefan. That's a neat piece of code. I struggle with the presentation layer problem. I don't want to include PHP code in my presentation layer. But it looks like that would be the best approach to pull in the language constants that I am looking for. That's really what this is about -- I'm hard-coding a login form into my theme but I would prefer it to be language independent.

Now that I think about it....and actually look through the XOOPS code, I think that you are right about a Smarty plugin. It should be relatively easy to write one that would retrieve a template by name.

That way we could include an arbitrary block template by invoking the plugin function with the template file name -- system_block_login.html for example -- as an argument. The plugin would pull the template of that name from XOOPS and insert it.

I guess that this is something that we should be bouncing around in the Smarty Help forum.

Thanks for your suggestions.

james

That's what I was affraid of. Oh well. As I said, this was something I would like to be able to do. No complaints.
thanks for your help.

In the System module is a block named Login.

I would like to explicitly include the template for that block in my theme.

I do not want to copy the template to my theme manually because I would like to use block variables such as $block.lang_username.

Can this be done?