1
tedmasterweb
Re: XoopsImage and image manipulation

Thanks for the pointer. As luck would have it, I had already downloaded and explored that exact module. While waiting for some pointers on XoopsImage, I've implemented my solution using ImageMagick.

Thanks for getting back to me though. Much appreciated!

Ted



2
tedmasterweb
XoopsImage and image manipulation

Hi,

I suspect this isn't exactly the best place to post this question, but I can't find anyplace else that seems better...

I need to do some image manipulation in a module I'm working on. I see in the XOOPS API that there are some objects named XoopsImage(etc), but the documentation is a bit sparse and the classes don't seem to be fully developed (to my inexperienced eyes).

Specifically, what I'm hoping to do is copy and resize an existing image on the file system and it seemed like XoopsImage would be just the tool, but I cannot figure out how to use it.

Does anyone on this list know how to do what I'm trying to do? I could probably do it with some of my own code, but I'd rather use the built-in tools (for a variety of reasons).

Thanks in advance.

Ted Stresen-Reuter
http://tedmasterweb.com



3
tedmasterweb
Re: Progress?

I too find the implementation of this particular feature confusing and struggled to get it to work as expected. I don't think this is the place for an official bug report, but to get the discussion going clearly, here is how I would describe the problem:

Preconditions:
- SSL is enabled and configured in System->Preferences
- User is not logged in and is viewing any page on the site
- "System->Preferences->General Settings->URL where SSL login page is located" is set tohttps://www.yoursite.com/extras/login.php (but this should be given the default URL of XOOPS_URL."/extras/login.php")
- login.php has its $path variable properly set

Expected behavior:
1. User clicks "Secure Login" link
2. System opens new window with SSL connection
3. System displays simple login form (username, password, submit button)
4. User fills in form and clicks "Submit" (or "Login" or whatever)
5. System authenticates user
6. System refreshes main page (now that user is logged in)
7. System closes the login window opened by the system in step 2

Actual behavior (2.0.7 and current CVS):
1. User clicks "Secure Login" link
2. System opens new window with SSL connection
3. System displays simple login form
4. User enters credentials and clicks Submit
5. System authenticates user
6. System displays text asking user to either log in or cancel
7. User clicks User Login button
+ Some browsers will complain at this point that the form is being sent in a non-secure way
8. System displays Close button
9. User clicks Close button
10. System refreshes main page with user now logged in

Postcondition:
- User is logged in in original window and has access to all password protected content

Recommendations:
- drop the new window login method in leiu of an SSL login module
- pop-up blockers may make this login method impossible
- user may simply close the login window (rather than clicking the Close button)
- a module integrates better with XOOPS than an extra




TopTop



Login

Who's Online

201 user(s) are online (127 user(s) are browsing Support Forums)


Members: 0


Guests: 201


more...

Donat-O-Meter

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

Latest GitHub Commits