Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 10/14/2021 in all areas

  1. It will take a couple Data Pages and a couple new fields in your user table. Confirmation code field unique is required random isn't exactly required, but it shouldn't be predictable Confirmation status field i.e. if confirmation_status !== 'confirmed' { do not allow login } An update Data Page to send the email with a link to the confirmation Data Page, set confirmation status to something like sent or pending, and add a unique value to the confirmation code field. Another update Data Page where the email will link members to that filters the user table by email and confirms the followed the magic link using the confirmation code. This Data Page would update confirmation status to "confirmed" Boom Hope this helps
    2 points
  2. Unfortunately I don't as there's a lot of other stuff going on. I'll see on Monday if I can create a stripped down version to post--that's a really good idea.
    1 point
  3. Are you talking about when you add a new element or page to the weebly site? Major changes like that would always require a refresh, I would believe. Or, do you mean, if a user updates a record in a report, or submits a form or something, they need to refresh to see the data? If that is the case, you don't have 'Disable AJAX Loading' turned on, on your datapages, do you?
    1 point
  4. I am experiencing this in one of the five accounts I work in. My experience is slightly different than your description as after about 3 minutes the objects would load and it was not all objects. Data Page editor, app parameters, and table design were all that I can recall. Support knows about this and I would assume are working hard to resolve it - not a minor thing.
    1 point
  5. I am using two different divs, but I haven't tried a specific container. Thank you! This helps a lot.
    1 point
  6. Unfortunately, I haven't figured out how to change them... without breaking things. Two work arounds that I use... Iframes I use iframes in most of my Caspio applications that rely on DataPages. <form id="caspioform" ... is not the only duplicated ID. Buttons and fields common to both data pages are also duplicated. Iframes let each data page be the only one in the page. Containers Simply putting the data pages into containers can help with this. <div class="dp-container" id="dp-1"> <script type="text/javascript" src="https://*******.caspio.com/dp/12345***************/emb"></script> </div> <div class="dp-container" id="dp-2"> <script type="text/javascript" src="https://*******.caspio.com/dp/12789***************/emb"></script> </div> This approach won't stop the error for non-unique ids, but you can now at least identify the elements accurately. const form1 = document.querySelector('#dp1 #caspioform'); const form2 = document.querySelector('#dp2 #caspioform'); Hopefully this helps!
    1 point
×
×
  • Create New...