You are not logged in.
Pages: 1
Hi, I have a recurring problem ever since we moved our site/database to a new URL. Some entries are not showing up in the the CMS when searching for them in their respective modules. If I look directly in the database, the entries are there. It seems like some sort of indexing/caching issue, but I don't know what steps to take to try and resolve this.
Any help would be greatly appreciated.
Thanks!
I got this working by creating a custom field type and made it add an error to $bigtree["errors"] when the email already exists. The only problem now is that it throws the error when updating the record. How can I make it only test the condition only when a new record is being added?
Thanks a million!
Thank you so much for aiming me in a good direction. I will explore both of these approaches and see which works best. If I get stumped I will post a follow-up in this thread, in case anyone else could benefit from it.
Thanks again!
Hi, I am new to this framework and I've taken over working on an existing site for a client. They have a public_users table and module set up. There is a public-user extension setup with a "classes/" directory and a PublicUser class that extends BigTreeModuledefined.
When a new user is added, we need to ensure that there is not already an existing user with the same email address. I'm having trouble figuring where to implement this validation, either in the backend, or if possible, frontend.
Any help would be greatly appreciated.
Thanks!
Daniel
Pages: 1