Hey all. I have taken quite a bit of time to read through the forums to see if I could get this answered without posting, but then I realized you have to know what you are looking for to search effectively.

That being said, please forgive me if this has been asked 1.2 million times.

I have some content that I built custom that uses some pretty basic php/mysql. I'd like to get it integrated in to my XOOPS 2.0.13 implementation.

Since I know you're going to ask why I'm using 2.0.13, let me answer. I use Invision Power Board for my old site and MUST keep all my current user base without requiring them to re-register. Hence, I had to use IPBM from bbpixel.com to keep this functionality.

Now on to the real question.

The test site is at http://test.statshub.com/index.php.

The content I need to integrate is at http://test.statshub.com/test/resort.php?resort_id=1

As you can see, I created a simple HTML block in the right column titled "Ski Areas". The content for those links is the resort site content that I also linked above.

My question is:

Considering the content uses GET to get the values (ie: '?resort_id=1') it needs to render the page. What is the best way to get this integrated in to the XOOPS site. It doesn't seem like a simple block will do the trick here.

I would really appreciate somebody to point me in the right direction here. If that somebody is also willing to lead me through this, I'd be interested in trading some graphic design work for you expertise.

Thanks ahead of time.

-Jeff

As expected, about 5 minutes after I posted this, I found this 'lil guy.

So now I have it working...cool.

http://test.statshub.com/resort.php?resort_id=1

Great, but...

Now I need to know how to make these pages only available to registered users. That seems tricky. I know that adding the XOOPS header/footer exposes some pretty cool API level stuff. Can somebody point me in the right direction for it please?

This is hardly an elegant option, but you could always put the link in a block that only appears when a user is logged in. Obviously, this is not secure, but if you're not overly bothered about a couple of non-users (who have seen this thread) accessing the page, then it could be for you.

I'm not completely sure if you can make blocks visible to only logged in users on XOOPS 2.0.13, but I'm not sure, so have a look.

A good option, but I'd much rather go a more secure custom route utilizing the API. I know it can be done, just not sure how to do it.