xcgal 2.02 and gallery for XOOPS both will automatically watermark (I think). I second the advice from another poster that perhaps you should download the top 3 modules and try them all out and see what they can do.

this is a huge feature gap for xcgal on xoops. i am running into this problem with XOOPS and it is frankly a:

no brainer feature. It also shouldn't be that big a deal to implement in the module, since the core function already exists in with the mid-sizing of the images.

i wonder if coppermine full version has this ability? Not sure about G2. . . though I use it on another site.

bump! I'm running into this problem. . why doesn't coppermine/xcgal have an option to automatically resize the user's uploaded image to a certain size? It already makes mid-size versions at a particular size. It shouldn't be that big a deal to have the ability to alter the root image, so that the gallery doesn't eat up all your disk space.

sounds like there is some interest in this type of module. it could be something like friendster or myspace or buzznet or any of the other very hip community sites that enable something akin to web pages for users while integrating blog, photo, networking. .

Sorry I won't be much help, but I am using this and I believe that it should update automatically, though I'm not sure that mine does on all implementations. You should go to the dev's site at:

www.xoopsforge.com

They are VERY helpful and committed to their modules.

that's so funny that you found that on google and not here. Even more funny is that that thread was started by ME! Didn't really go anywhere with my particular security token problem.

I'm sorry to hear about your problem with the "no valid security token errors." I can empathize with you because though my problem with this is not nearly as bad, it certainly could be a site killer and sounds like it in your case.

I've been dealing with this for a long time and have reported it as an official bug but it has not been "assigned" to anyone and I have not heard any responses as to how to fix it or even start to track down the problem. It seems to be a problem that is isolated to specific, limited sites (perhaps server configurations) and impacts site functions differently in each case, like comments, notifications, log-in, registration, browser types, etc., depending on who knows what.

I upgraded to 2.3 and don't know if I still have the problem or not. My users don't bother telling me about it anymore as it only relates to comments on Firefox. Go figure.

My sense is that the problem, though highly significant for those that it impacts, is very limited in the number of xoopsers affected and therefore is not really getting attention. Also, my guess is that the security token function may be something that only a few XOOPS devs really have experience with. Not sure where you should go for help, but let us know if you find it or can raise this issue up higher on the priority list.

Does anyone know of a good and easy to use web page maker script for XOOPS that let's members create their own web page to be hosted either on a subdomain such as yoursite.xoopsite.com or somewhere else on the XOOPS managed site?

I haven't seen anything like this but would like to give my users this feature.

If not a module for xoops, does anyone know of a good open-source solution generally?

yes, it's definitely worth a try. I have tried every combination of custom sessions imaginable, on/off, long/short, etc. and it doesn't resolve my token error issue on XOOPS comments.

But definitely try it out.

I saw your post on my bug entry on the dev log. So far, a lot of bugs have not been "assigned" including this one. I posted it there after a month or so of not being able to fix it. I don't know if this issue has gotten any attention from the dev side of the house. So far, the only repsonses have been from users who have the problem. I don't think there are many here who are familiar with the security token functionality, hence the lack of response.

My issue is primarily with Firefox and not as much with IE, though it does happen on any browser. Sadly, I have to recommend to people NOT to use Firefox and use IE instead. . Go figure.