Hello!
First of all I will thank you for a lovely component for joomla, this have saved me a lot of work.

Now to the problem, I have installed all components and they are working fine. Except for a little small thing, the participants list in the frontend. When you want to show this it doesn't show anything, only the result of how many participants is on the lan, next button and so on.

I have added columns in the backen and they are showing correctly, except the users then. I need help, what could be the problem?

Kind regards, Hamatzu!

I have the exact same problem which seems to be unrelated to the previous posts concerning not being viewable in the front or backend. I've changed all the (array) fields and it makes no difference.

Fixed this. There is an error in the preparation of the SQL script. If you have communitybuilder installed, I first try to join the #__comprofiler table to the user table, but then only in the next line join the user table, this creates an SQL error. To fix, edit the mls_events.php and replace the lines around 208 - 220 with this:

Code:

//Select records $query = "SELECT p.*," .$seatSql ."\n u.name AS `joomla_name`,u.username AS `joomla_username`,u.email AS `joomla_email`,u.id AS `joomla_userid`," ."\n p.subscribed_time AS `mylansite_subscribed`,p.checkin AS `mylansite_checked_in`,p.checkout AS `mylansite_checked_out`,p.paid AS `mylansite_paid`," ."\n e.name AS `eventname`" .$cbsql1 ."\n FROM `#__mls_events_participants` AS `p`" ."\n INNER JOIN `#__mls_events` AS `e` ON e.id = p.eventid" ."\n INNER JOIN `#__users` AS u ON u.id = p.userid" .$cbsql2 ."\n" . $where ."\n ORDER BY p.subscribed_time" ."\n LIMIT $pageNav->limitstart, $pageNav->limit";

Thanks for the update- I made the change but the participants still do not show up on the front end. You are right that I have Community Builder Installed but the changes didn't help. Any more ideas?

I had the same problem.. but after downgrading to 1.0 , it's now showing again..

You need to create at least one field within communitybuilder, this is still a defect and has to be fixed. Unless one field has been created by you, the query will fail.