Jump to content

ClayG

Members
  • Posts

    19
  • Joined

  • Last visited

  • Days Won

    3

ClayG last won the day on November 3

ClayG had the most liked content!

  1. Has anyone figured out a way to reduce or prevent duplicate user accounts when you let users register a login account in your Caspio app? My app records employment history of school leaders, and those same school leaders can login to review and update their info. Quite often, a user will end up creating a new sign-in account because their email address has changed, or because they don't remember if they have a login account and they create one with a different email address. Currently, I have to clean this up manually by deleting their newly created account, and then I enter their new email address onto the original user account. Has anyone tackled this issue with something more automated?
  2. This is awesome! After testing it, I found that the password was saving, but not my username field. So I had to discover that my username field was called xip_Login_username in the browser rather than just #xip_Name, and after clearing bad cookie, it worked!
  3. I wish I had an answer for you, but I just wanted to share that I haven't run into that problem at all. So I'm not sure what the culprit might be.
  4. Has anyone else used Weebly as your CMS for your Caspio datapages with the desire to leverage Caspio authentication to show/hide menus? Weebly has its own built-in login/registration functionality, which includes the ability to create user groups, and if you do, you can set Weebly website pages to only be accessible for certain groups. When one of those pages is in the navigation menu, it remains visible, and users are prompted to login if they click on it. And when you use Weebly for user login/registration, it's a pretty basic registration process that just asks users to enter an email and password. I'm building a Weebly website which contains a mix of datapages. Some datapages don't require authentication, but most do require authentication. This howto article from Caspio on restricting access to users based on their role was very helpful, and I'm leveraging it. What I wish I could do, is show/hide Weebly menu choices based on a user's role within my Caspio application. I'm somewhat close to figuring things out, but it feels rather kludgy. Is there a more elegant / secure way? Within the particular Weebly theme I'm using, a main navigation choice can be hidden with a line of CSS like the following: .wsite-menu-item-wrap.wsite-nav-4 { display: none; } /* THIS HIDES MAIN MENU CHOICE #4 */ And this would restore/show that main navigation choice: .wsite-menu-item-wrap.wsite-nav-4 { display: inline-block; } /* THIS RESTORES MAIN MENU CHOICE #4 */ And as an aside, you can even hide the entire Weebly menu with a line of CSS like this: div#navlist { display: none; } With the above in mind, one tactic I've tried is to edit the Weebly theme's main CSS so that a particular menu option is hidden by default, and then I have a page with a Caspio datapage that is configured to require authentication, and within the "Configure Fields" screen of that datapage, I'll have a Header/Footer with the CSS that restores the menu choice to visibility. Kludgy? Yes. Secure? No. The pages that I want to hide from people who haven't logged in don't have Caspio datapages on them, otherwise this would be easier. Has anyone else tackled this, or have any suggestions?
  5. Thanks! That sounds very workable.
  6. Has anyone successfully done a live feed or a scheduled data sync from Caspio to Google Data Studio? I have a consultant who has created some data visualizations for us in Google Data Studio using an exported copy of data from Caspio, but now we want to try and either do a scheduled data sync or a live feed, and we're not sure where to go next.
  7. Thanks! That article about separating the search page vs results page would probably also work for me since google analytics would likely capture those URL strings and that would be adequate for reviewing how people are searching.
  8. We're getting ready to launch a solution we built in Caspio. Users will be able to search people records using a variety of search fields. My boss is asking if there's anyway we can see a log of the search criteria that users try. We don't have the Grow plan currently, so we don't have the user activity log feature, but I'm doubtful it would show that level of detail. Does anyone know and/or have you tried to record the search criteria that users submit in their record searches?
  9. For anyone who reads this thread later.... I did find working code for Weebly websites for changing the home page href link of the logo (or site title) to point to the user's landing page, rather than the usual "/" home page URL. <!-- redirecting the logo to someplace else --> <script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.7/jquery.min.js"></script> <script> $(document).ready(function() { $(".wsite-logo a").attr("href", "/admin-page.html"); }); </script>
  10. Thanks, the part of this setup that I'm still pondering is how to handle a home page. Traditionally, a website's logo will be something that users can click to return to the home page. But when you're creating different landing pages for your roles, are you using some Javascript to change a home page link or logo to point to the user's landing page?
  11. kpcollier, For your datapages that are truly universal in their purpose (e.g., Change Password, or maybe an Update Profile), did you create unique versions for each user role?
  12. Awesome, I really appreciate your write-up!!! I will pursue the same approach and let you know how it goes!
  13. Thank you both! I had planned to use the user-specific redirect after login, and I have it partially set up. The thing I'm wrestling with now is wanting to use a website platform like Weebly to host the site. Since I want to have different menu options for an Admin vs a Regular user, I'm trying to figure out whether to create my menu options for the site in Weebly, but then use CSS to hide menus that a regular user should not see (which doesn't sound like a very security conscious way to go). Or, should I create my menu choices in Caspio using the App Parameters feature? That seems like a more security-minded approach and I have played with that a bit. This is my first significant app for me in Caspio. I've watched the videos from Ned who shows how he has hand-coded HTML pages for different users, and while that approach looks straight forward, I would really prefer to host the website with a nice CMS, like Weebly or Wordpress.
  14. As I've been building a prototype application, I originally created 3 different tables for the 3 kinds of users (people) in my app, but now I'm thinking that was a bad idea and it would make more sense to just have a single table of all people but have a column for their "Role" which I would leverage for what level of access they will have to datapages, etc. To give a little more context, I currently have 3 tables: School leaders (with profile fields that are pertinent to them) Consultants (with profile fields that are specific to them) Staff (internal staff who will need to login to add/edit info) All 3 user groups above will need to login but they'll be given different menu options. I realized after attempting to create an Authentication that there can only be a single data source for the usernames and passwords, so it probably makes more sense to put all my different users into one table and then create views that specifically filter on my 3 types of users for my datapage needs?
×
×
  • Create New...