This meeting summary revolves around the State Changers troubleshooting an integration issue on WeWeb with an external service - Outseta. One participant was experiencing an issue where the Outseta login was not rendering correctly in WeWeb application. Despite the script appearing correct in the code and console, the login form did not appear on the web page.
Possible solutions which were discussed and attempted include: 1. Making sure the code script is in the appropriate section, not duplicated. 2. Checking the ID and height settings of the "div" where the code was embedded. 3. Attempting to use a "setTimeout" function to allow the page to fully load before the form script is run. 4. Trying different methods of declaring the variable holding the authentication settings, including declaring it as a global (window) variable. At the end of the discussion, it was decided that these issues could represent a bug in either WeWeb, Outseta, or both. The participant planned to contact Outseta support with detailed information to get assistance. Another participant suggested it might be related to issues with other HTML elements not rendering correctly in WeWeb. The team also planned to continue investigating and discussing potential solutions. The meeting involved use and mention of the WeWeb platform and Outseta integration. Although no other keywords like "Xano", "FlutterFlow", "Zapier", "Make", "Integromat", "Retool", "Bubble", "Adalo", "AppGyver", "AppSheet", "Comnoco", "Fastgen", "Firebase", "Google", "OAuth", "Stripe", "Twilio", "Airtable", "DraftBit", "Javascript", "Typescript", "React", "Vue.js", "JSX", "HTML", "CSS", "lambda", "serverless", "State Change", "ScriptTag", "OpenAI", "AI21", were mentioned in this specific meeting.
(Source: Office Hours 6/28/23 )
