Re: working on yogurt module
  • 2009/5/14 18:01

  • pablo103

  • Not too shy to talk

  • Posts: 181

  • Since: 2008/2/3 1

Well, Google friend connect would me a good alternative, but there is no interest of XOOPS developers so far. Have a look at this http://www.google.com/friendconnect

Re: working on yogurt module
  • 2009/5/14 18:33

  • NetButch

  • Just popping in

  • Posts: 12

  • Since: 2007/4/2 1

Elgg may be a good start, has anyone looked at creating a XOOPS module from the ELGG code?

you can try elgg at my test site http://www.netbutch.com/eggs


Re: working on yogurt module
  • 2009/5/14 21:39

  • Kiwi_Chris

  • Just popping in

  • Posts: 79

  • Since: 2009/1/3 2

the google gadgets is not bad if your not running a social website and you want to add some social aspects.

Elgg, is a good system but as I am in a shared webhosting my host advises I can not run it.

Re: working on yogurt module

im already building a major Elgg site
and trying to get XOOPS around it
but i dont see it working without a MAJOR MAJOR re-coding

Re: working on yogurt module
  • 2009/5/16 4:37

  • Kiwi_Chris

  • Just popping in

  • Posts: 79

  • Since: 2009/1/3 2

Problem with Elgg is its not much good on a shared hosting environment. Even on the sites that support it advise this.

Then it becomes a price thing - because you start needing VPS or Dedicated Hosting.

Re: working on yogurt module
  • 2009/5/26 17:56

  • xgarb

  • Not too shy to talk

  • Posts: 154

  • Since: 2003/3/30

kudos to people who are putting their time into Yogurt but I think it is missing the point of XOOPS in that you have the core and then you add the bits you want to make the site you want. Some might choose one module over another for a purpose (ie one gallery module might be chosen for it's simplicity or another for features). Sticking loads of functions into one module stops this from working.

My opinion is the basic social networking features should be built into the core so modules can call on them as necessary.

Functions such as Comments, Ratings, Recommendations, Polls, Member links, Tags, Notifications etc should have basic versions in the core that every module can hook into. These should be written in a way that enables enhanced versions to be dropped in as modules.

It's tricky to get the balance right between a streamline core and having basic functionality that all modules have access to.

I mentioned this a looooooong time ago but XOOPS for me was always a Community Management System rather than a Content Management System.

Re: working on yogurt module
  • 2009/5/30 22:13

  • TheShadow

  • Just popping in

  • Posts: 36

  • Since: 2009/1/23

I am sure if somebody offers to pay for a such conversion, there will be developers who will be willing to do it, because they would treat it just as another client engagement.

Mowaffaq offered 1000 USD to develop Yogurt.
Maybe you guys missed his offer.

Re: working on yogurt module
  • 2010/1/4 9:13

  • aslani606

  • Just popping in

  • Posts: 26

  • Since: 2007/4/29


develop Yogurt.????!!!

Re: working on yogurt module
  • 2010/1/4 15:45

  • ipwgc

  • Quite a regular

  • Posts: 216

  • Since: 2005/8/13

SocialNet 2010, is not the same thing that yogurt,

1. The codes were translated from portuguese to english and changed for $socialnet

2. The names and the codes were changed and adapted for the integration of the 11 modules and sections that are participating of the SocialNet project.

3. In SocialNet 2010 doesn't exist any sentence or word related to yogurt.

4. Fallow the turorial from here, I'm working on this tuturial for USERS and for WEBMASTERS

5. Prove and download from here http://www.ipwgc.com/socialnet/modules/TDMDownloads/

David Yanez Osses


Who's Online

690 user(s) are online (49 user(s) are browsing Support Forums)

Members: 0

Guests: 690



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

Latest GitHub Commits