1
tommyb
Per-Group Public, Private Module Section Setup
  • 2005/4/25 17:23

  • tommyb

  • Just popping in

  • Posts: 7

  • Since: 2005/4/19


Hello all,

I'm setting up my first XOOPS site and would appreciate some general guidance from a veteran Xoopser.

I plan to offer an Image Gallery, a File Upload/Download Area, Discussion Forums, FAQ section, Resource Reservation System, an Events Calendar, and other common features that the wonderful XOOPS provides.

I will be creating around 40 user groups. I'd like for each group to have publicly and privately accessible sections of each of the above-mentioned features. This would allow each department of my company to make certain information available company-wide as well as other information being available exclusively to their staff members. I want each department's submissions to be clearly identified/searchable.

It appears that I have to repeat a lot of setup steps to accomplish this. I have to go into the System Admin-Groups section and create a security group. Then, I have to go into the download module and create a MAIN category for the group, then "Public" and "Private" SUB-categories, then specify which security groups do what with each category/subcategory. Then I have to go into AMS and setup Topics and SUB-topics and their associated security group rights. Similar operations will await me in each of the other modules.

Is there an easier way of accomplishing this or having it be a more automated process? I would think this would be a common need for any company intranet based on Xoops.

Many thanks in advance for all advice!



2
tommyb
Per-Group Public, Private Module Sections
  • 2005/4/25 1:56

  • tommyb

  • Just popping in

  • Posts: 7

  • Since: 2005/4/19


Hello all,

I'm setting up my first XOOPS site and would appreciate some general guidance from a veteran Xoopser.

I plan to offer an Image Gallery, a File Upload/Download Area, Discussion Forums, FAQ section, Resource Reservation System, an Events Calendar, and other common features that the wonderful XOOPS provides.

I will be creating around 40 user groups. I'd like for each group to have publicly and privately accessible sections of each of the above-mentioned features. This would allow each department of my company to make certain information available company-wide as well as other information being available exclusively to their staff members. I want each department's submissions to be clearly identified/searchable.

It appears that I have to repeat a lot of setup steps to accomplish this. I have to go into the System Admin-Groups section and create a security group. Then, I have to go into the download module and create a MAIN category for the group, then "Public" and "Private" SUB-categories, then specify which security groups do what with each category/subcategory. Then I have to go into AMS and setup Topics and SUB-topics and their associated security group rights. Similar operations will await me in each of the other modules.

Is there an easier way of accomplishing this or having it be a more automated process? I would think this would be a common need for any company intranet based on Xoops.

Many thanks in advance for all advice!



3
tommyb
Re: Changing allow_url_fopen state on shared server
  • 2005/4/25 0:41

  • tommyb

  • Just popping in

  • Posts: 7

  • Since: 2005/4/19


Thanks for the clarification TL. That takes care of that!

Goodbye iPowerWeb...



4
tommyb
Re: Changing allow_url_fopen state on shared server
  • 2005/4/24 22:42

  • tommyb

  • Just popping in

  • Posts: 7

  • Since: 2005/4/19


Hey m0nty,

Thanks for the tips!

I tried the .htaccess mod as well as the php.ini file with no success.

FYI, I successfully added "php_flag register_globals off" to the .htaccess file to satisfy one of the other checks performed by the Protector module. Does that item working indicate the "Allow_url_open" entry should work as well?



5
tommyb
Re: Changing allow_url_fopen state on shared server
  • 2005/4/24 20:00

  • tommyb

  • Just popping in

  • Posts: 7

  • Since: 2005/4/19


Thanks for the confirmation that it is something they should do for me and in fact, would HAVE to do as I can't do it.

It's been surprising to me that they weren't more knowledgable. They're supposedly one of the three largest hosting companies out there.

I'll be looking into alternatives now.

Thanks again,

Tom



6
tommyb
Changing allow_url_fopen state on shared server
  • 2005/4/24 2:54

  • tommyb

  • Just popping in

  • Posts: 7

  • Since: 2005/4/19


Hello all,

I'm new to XOOPS (and PHP, and Smarty, and...etc.). I've installed GIJoe's Protector module on a test site and it indicates that "allow_url_fopen" should be disabled.

My site is on an ipowerweb shared Linux box. I sent an email to their support staff requesting they disable this command for my site.

iPowerWeb's responses have ranged from having no idea what I'm talking about to telling me that it is my responsibility.

I'm figuring that if I can control it at all, it requires some combination of the creation/modification of php.ini and .htaccess in my public_html directory, but nothing I've tried has worked. Either it's still on or I get a 500 error.

Any help or suggestions would be greatly appreciated!

Tom Baggett




TopTop



Login

Who's Online

223 user(s) are online (149 user(s) are browsing Support Forums)


Members: 0


Guests: 223


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: May 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits