Hi all,

Just updated to MySQL 4.1.12, PHP 5.0.4, Apache 2 and had some problems with connecting to MySQL from XOOPS and phpMyAdmin.

I have been trawling the web for answers and wondered if any other XOOPS users on OS X 10.4.4 had encountered this;
after years of use XOOPS can't connect to the database.

I can use MySQL on the command line, so that is working, it's the connection/socket thang. phpMyAdmin gave this error:

Quote:

This I have finally fixed by specifying an path to the mysql.sock socket in the MyAdmin config file:

Quote:

I feel that if I could specify a similar socket in XOOPS that I could get the connection to work. Any ideas?

My live sites are all working fine, and I've moved them around loads in the past, but this one has me stumped. I think that it is a OS X specific problem.

I am using a heavily adapted version built on XOOPS 2.0.6

All help and commiserations welcome, but no OS X jokes...

Best,

Kingpig

Hi all

We really want to release the core hacks which basically enable the membergroups module. But we are unable to work on it at the moment.

I must also warn you that because of complexity, there will be no easy way for you to develop it apart from rolling up your sleves and tinkering with the code. I don't think releasing it at the moment would provide a quick fix for anyone. We will try and document it more, tidy it up and then release it.

Thanks for your patience,

KingPig

I think that we extended 2.0.6 - so probably a lot of water under the bridge since then.

Kingpig

thanks for the questions

Quote:

here are some quick answers

1. membership has two stages: registered and subscribed. a registered user has signed up but never paid OR a lapsed subscribed user. only subscribed users can edit the site's content modules. once a member's subscription ends they are no longer allowed to edit their profile or content BUT may log in to re-pay their subscription. It is very much like the inactive user status. control of which group a member belongs to has been developed from the pre-existing XOOPS group classes - i think the same ones that control 'webmaster', 'friend of xoops', 'anonymous' etc.

2. our site only uses pay-pal at the moment and there is no quick way (gui) to change it. however as the system is based on passing messages back and forth between sites, I am sure it wouldn't take too much work for you to change it for your payment people. pay-pal does seem to be quite good though, and users do not have to create an account now to make a payment. this makes it much quicker.

i would also like to say that the membergroup module is very complicated and extends core XOOPS classes and pages. i don't know how portable it is going to be. it also has quite a complex set of inheritances. only a small amount of it is controlled through the admin section most work is done in the classes.

having said this though, we will still try and get some things out, but the whole module for membergroups will take a while.

best wishes

kingpig

Hello

Thanks for your kind comments.

Because we have been so busy there has not been time to tell people about the work we have been doing and release information about it.

Mr. Loop and I have been working for over a year now on the newworknetwork (nwn) site and a lot has been done on the membership/registration process. Some of the features include:

+ connection to paypal to validate registration.
+ back-end membership management to manually process subscription. (nwn is a not for profit artist-led organisation but does have a £10 per year subscription fee).
+ an equal opportunities form to monitor the ethnicity, gender etc of our members.
+ extended view permissions for sensitive member details e.g. some users like to keep their home address private while others don't mind other members seeing it.
+ a REALLY long disclaimer
+ the use of our 'check box group' classes. e.g. artform interest (theatre, music, installation etc.), region (scotland, wales, london etc.). These are necessary as the check box groups are used in other new modules and are stored as many - to - many relations in the database. i.e. we maintain one list of artforms and store relations between each and other entities in link tables. This has lead to a database of hundreds of tables, but is very maintainable. see how it works in the module searches.

Mr Loop has also been developing a huge new module called membergroups which has enabled us to have profiles for groups of individual members e.g. a profile for a theatre company. membergroups directly from the user class and extend it dramatically. they are useful as now a member may 'switch' to their membergroup's profile to create content on the group's behalf.

a membergroup still has a user profile, uses the XoopsUser object and therefore behaves like a normal XoopsUser but an unlimited amount of other users may be associated with it. e.g. theatre company x has its own profile and is it's own XoopsUser but may also be linked to the profiles of it's employees.

i am probably not making this very clear. if you go to the site look at the company, venue, network and organisation profiles you can see this in action. (it should be noted that a lot of our users haven't figured out how to use this yet, so there are not many examples yet - but it has great potential)

we have also made quite a lot of new modules which we also want to share soon.

please ask more questions and we will try to find a way to release the code hacks soon. (how should we do this? we haven't done it before)

Thanks again and thanks to all the other community members that have helped us along the way.

best wishes

robert aka KingPig

Since I changed some of the date formats in Agenda-x day, week and month view events are all pointing to event 1. That is to say that newly added projects cannot be accessed. The correct link appears with the event title (events are added to the database) but the link target is always event id 1.

Any one else run into this problem? Any ideas?

KingPig

Don't know if this is for beginner's corner, but I still feel like a beginner.

I have just implemented comments for an area on my site. The refresh button works (even though there are no comments yet). But 'post comment' doesn't. I get a blank page.

I did some tests to check why comment_new.php wasn't working. It turns out that neither XOOPS_ROOT_PATH or is_object($xoopsModule) seem to be appropriately set. So the code exits before it does anything.

Does anyone know of a reason why these two variables aren't set? I used XOOPS_ROOT_PATH on the page that called comment_new - where has it gone? Surely I am still in a module - or did it vanish?

best,

KingPig

I know that this has probably been answered before, but i am having problems finding an answer using search.

I have made some changes to the uploader class, creating getHeight and getWidth methods. However my changes don't seem to trickle through.

Do these classes need to be re-loaded (like a module update) before they work? If so how do I do it?

Cheers

KingPig

Thank you Mithrandir

Anything that helps clarify XOOPS design to newbies is most appreciated

thanks from glasgow

kingPig

Thanks for all the messages! Being a newB I thought that no-one was listening - how wrong I was.

I have figured most of it out now, basically what was suggested in the forum linked to above.

https://xoops.org/modules/newbb/viewtopic.php?topic_id=20250&forum=27&post_id=88208#forumpost88208

I have been playing with NoAh, and wonder whether it is possible to quickly change details using that?

NoAh is very interesting.

Cheers

KingPig