11
pstrasma
Gallery with working Xoops search?
  • 2003/12/26 21:17

  • pstrasma

  • Just popping in

  • Posts: 24

  • Since: 2003/12/23


I choose to use Gallery 1.3.3 on my site as it was the most popular graphics module in the download section. After using it, I noticed that the search function is not integrated with the main XOOPS search. Reading the forums, I see that there are a few other bugs in 1.3.3 that other users have hacked. I also see that there is talk of a new, better-integrated gallery module for XOOPS 2.1 along with several other heavily used .

So, has anyone hacked Gallery 1.3.3 to use the main search?

Alternatively, what is the status of the new module? Will it use the main XOOPS search function?

Thanks!




12
pstrasma
Re: Unable to edit or delete user profiles from user details view
  • 2003/12/26 0:12

  • pstrasma

  • Just popping in

  • Posts: 24

  • Since: 2003/12/23


This problem only exists on the specific page I mentioned--viewing profile details (reached by clicking on username from member search results). Admin interface and search results links both work normally.



13
pstrasma
Unable to edit or delete user profiles from user details view
  • 2003/12/25 7:41

  • pstrasma

  • Just popping in

  • Posts: 24

  • Since: 2003/12/23


When viewing user details from userinfo.php as an admin, the edit profile & delete user buttons do not work.

This seems to be due to an error in the system_userinfo.html template, which only writes the line 3 <form name="usernav" action="user.php" method="post"> tag if the viewing the user's own page. The elseif used to check if the viewer is an admin does not have a <form> tag.

I have corrected this by modifying the line 23 <{elseif $xoops_isadmin != false> and adding another form statement as follows:
<{if $user_ownpage != true && $xoops_isadmin != false}>
<
form name="usernav" action="user.php" method="post">


On a similar note, after fixing this I noticed that if an admin edits another user's profile, the admin userid is automatically entered into the nickname field on the update user form. Unfortunately, I have no solution to suggest for this bug.

IMHO, it probably adds needless complexity to have all these editing and account management functions on a viewing page. The Avatar upload function should just go in with the rest of the profile editing on in edituser.php. The delete user function can also go on that screen. The Inbox,



14
pstrasma
Re: WF-Channels in Core & Contact Us module
  • 2003/12/24 0:08

  • pstrasma

  • Just popping in

  • Posts: 24

  • Since: 2003/12/23


Apologize for the cross post, but my comments on WF-Channels seem more appropriate here.

Basically, I'd like 2 things from the 2.1 modules. First, I'd like to see the Contact Us module beefed up into a total About this Site package. Second, I'd then also like a robust way build / wrap content pages whether this is provided by the new Sections, WF-Channels, or some other add-in.

Quote:
A few things strike me as good ideas after playing around with this module [WF-Channels] on my site (http://piquant.us/imsa/):

1) Integration to Contact Us module & Site Info block
There is an overlap of intended functionality between these three parts. WF-Channels should superscede the "refer a friend" function of the Site Info block. And why not enable a WF-Channels about link and the Contact Us link in that block as well? I've done by editing the templates and hinding the other modules; however, it would be much cleaner if 3 three parts were integrated.

2) Ability to manage multiple top-level content trees
Often there is a need for more than one content trees. If possible, it would be helpful to have the option to make each channel a parent with it's own main menu link. For example, I am currently implementing my site's "About this Site" content tree with WF-Channels and the "Reunion 2004" content tree with TinyContent. I next need to add a third tree with another set of content. It would be ideal to manage all these pieces in the same module, sharing the same set of templates, images, etc...

3) Separation of About, Refer, Link (& Contact Us) functionality
Counter to my above statement, it does seem like these pages are truly specialized. Features like RSS generation out of the news module are great but pretty unrelated to the general content function. So maybe it would make sense to split this project into 2 separate modules, WF-Channels & say WF-About? WF-Channels should become the generalized content manager with multiple trees in point #2 and WF-About could become to specialized about this site module.

Just my $0.02. Great work!



15
pstrasma
What is consensus about Headlines module?
  • 2003/12/23 20:26

  • pstrasma

  • Just popping in

  • Posts: 24

  • Since: 2003/12/23


Like others here, I am experiencing erratic behavior with the Headlines module. Reading through the posts though, it seems like there are several theories, but few answers about what is happening here.

Here are my results:
Failshttp://myrss.com/f/i/m/imsaMainOet9kz1.rss
Workshttp://www.piquant.us/feeds/gnews2rss.php?num=15&q=%22Illinois+Mathematics%22+%22Science+Academy%22
Workshttp://piquant.us/shades/index.rdf
Workshttp://piquant.us/imsa/backend.php

So I've had success with the XOOPS feed, stock RDF, and a Google News php-based scrape. The only thing that fails is the myrss server-generated rss file.

Any ideas?



16
pstrasma
Re: Does WF-Channel support blocks?
  • 2003/12/23 18:18

  • pstrasma

  • Just popping in

  • Posts: 24

  • Since: 2003/12/23


A few things strike me as good ideas after playing around with this module on my site (http://piquant.us/imsa/):

1) Integration to Contact Us module & Site Info block
There is an overlap of intended functionality between these three parts. WF-Channels should superscede the "refer a friend" function of the Site Info block. And why not enable a WF-Channels about link and the Contact Us link in that block as well? I've done by editing the templates and hinding the other modules; however, it would be much cleaner if 3 three parts were integrated.

2) Ability to manage multiple top-level content trees.
Often there is a need for more than one content trees. If possible, it would be helpful to have the option to make each channel a parent with it's own main menu link. For example, I am currently implementing my site's "About this Site" content tree with WF-Channels and the "Reunion 2004" content tree with TinyContent. I next need to add a third tree with another set of content. It would be ideal to manage all these pieces in the same module, sharing the same set of templates, images, etc...

3) Separation of About, Refer, Link (& Contact Us) functionality
Counter to my above statement, it does seem like these pages are truly specialized. Features like RSS generation out of the news module are great but pretty unrelated to the general content function. So maybe it would make sense to split this project into 2 separate modules, WF-Channels & say WF-About? WF-Channels should become the generalized content manager with multiple trees in point #2 and WF-About could become to specialized about this site module.

Just my $0.02. Great work!



17
pstrasma
Re: Does WF-Channel support blocks?
  • 2003/12/23 16:08

  • pstrasma

  • Just popping in

  • Posts: 24

  • Since: 2003/12/23


That is the sort of solution I'm considering. I want a prominant "about this site" block to appear front and center for new unregistered users. Registered users will then access this message from a WF-Channel about this site default page.

To be implemented athttp://piquant.us/imsa/ once I figure out where that channel content is stored.



18
pstrasma
Re: Alumni Reunion Site
  • 2003/12/23 8:13

  • pstrasma

  • Just popping in

  • Posts: 24

  • Since: 2003/12/23


Admittedly, I did the general CMS research prior... 2 days sunk implementing XOOPS for the site so far.



19
pstrasma
Alumni Reunion Site
  • 2003/12/23 7:18

  • pstrasma

  • Just popping in

  • Posts: 24

  • Since: 2003/12/23


Hats off to the XOOPS team!

48 hrs ago, my 10 yr reunion committee was tossing around ideas for reconnecting prior to and after the reunion. Forums, photo galleries, etc... sounded cool, but would be a lot of work, right?

After researching several CMS systems just to see what was possible, I took a chance and installed Xoops. Even without a complete manual, the installation went flawless! My only challenge has really been coming up to speed on what modules do what and working in other content pieces.

That said, the IMSA 1994 Alumni Portal is now live. Please take a look and constructively critique!

For those interested, I choose to implment the modules: news, TinyContent, TinyCalendar, Forums, Gallery & my Links publicly. On the TinyContent pages, I used inline frames to punch out to some existing sites such as our school's alumni database & a sophisticated survey tool. The registration page is just a form tied to the PayPal shopping cart system. Behind the scenes, Document Management System is running to support the planning committee's efforts.

--Paul Strasma



20
pstrasma
Re: Ok we are LIVVVVVE!!!!!!!!!!!
  • 2003/12/23 6:39

  • pstrasma

  • Just popping in

  • Posts: 24

  • Since: 2003/12/23


I for one like both your approach and the theme. What theme did you build this around?




TopTop
« 1 (2) 3 »



Login

Who's Online

180 user(s) are online (105 user(s) are browsing Support Forums)


Members: 0


Guests: 180


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