I am looking for a solution to have both Sellers Listings and Buyers Listings in phpwslistings. I tried to give different class_id to Seller and Buyer. And gave them different formelements. But it is definitely not a good solution to save Sellers and Buyers data in one mod_listings table. Can anyone give me some advice?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't really follow why it wouldn't be a good solution to save Buyers and Sellers data in the same table. If you could expand on why this is a problem, and explain what exactly your needs are, I may be able to give you some advice.
Wendall
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In my case, the Buyers are who looking for place to rent/buy, the Sellers are property owners and want to lease/sell their property. If I put both Buyers and Sellers data in one mod_listings table then when I'm doing Manage Listings it is difficult to distinguish from them. Besides, the Random Block will mix different class listings and this result is not what I want. I am trying to install two phpwslistings modules, one for Sellers another for Buyers. Do you think this is a good idea?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The product won't currently support what you are trying to achieve. Perhaps we can add an option on the class table to exclude a certain class from the random listing block. Better yet we should have options to have a random block for each class. Also, we could build in the ability to manage listings by class.
If you would put this in as an RFE, we will add this to the product ASAP.
Wendall
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am looking for a solution to have both Sellers Listings and Buyers Listings in phpwslistings. I tried to give different class_id to Seller and Buyer. And gave them different formelements. But it is definitely not a good solution to save Sellers and Buyers data in one mod_listings table. Can anyone give me some advice?
I don't really follow why it wouldn't be a good solution to save Buyers and Sellers data in the same table. If you could expand on why this is a problem, and explain what exactly your needs are, I may be able to give you some advice.
Wendall
In my case, the Buyers are who looking for place to rent/buy, the Sellers are property owners and want to lease/sell their property. If I put both Buyers and Sellers data in one mod_listings table then when I'm doing Manage Listings it is difficult to distinguish from them. Besides, the Random Block will mix different class listings and this result is not what I want. I am trying to install two phpwslistings modules, one for Sellers another for Buyers. Do you think this is a good idea?
The product won't currently support what you are trying to achieve. Perhaps we can add an option on the class table to exclude a certain class from the random listing block. Better yet we should have options to have a random block for each class. Also, we could build in the ability to manage listings by class.
If you would put this in as an RFE, we will add this to the product ASAP.
Wendall