“You must be logged in as the user you’re trying to install to” Error When Attempting OAuth
Attempting the OAuth flow results in this error.
This error can occur when:
- You have a Weebly URL enpoint hardcoded in your callback.
- You didn’t pass the client_Id parameter in the URL. The client ID is needed to understand who you are attempting to authenticate.
- Always use the URL sent from Weebly in the response. Weebly enpoint URLs may change over time, so the OAuth flow does not allow hard-coded URLs.
- Make sure the
client_idparameter is included in the URL For more info, see App Authorization and Install Flow.
Settings Don’t Display Correctly in the Dialog
You’ve created settings in the manifest, but the dialog is empty
This error can occur when you haven’t included your settings in a group. Your manifest must contain at least one group.
group property as a parent to the settings. The group property is what defines the properties to display on a single dialog page.
Note in this example that the parent property is a group (
type=group) and the child is the actual setting. The label of the parent group property (in this case “Display”) is what is used as the title for that group’s dialog page.
For more info, see Create Element Settings.
“Element version is required” Error When Attempting to Upload the App’s Zip file
You see this error in the Developer Portal when you try to upload the zip.
When you see this error, it’s likely because you did not include a version for both your app and your element. Both require a version number:
For more info, see Add an Element to the Manifest.
Other Errors When Uploading Your App’s Zip
You see a different error when trying to upload the zip
Check the following:
- There are known issues when using Chrome. If using Chrome, try a different browser.
- Make sure your element settings belong to a parent Group setting. See Settings Don’t Display Correctly in Modals, above, for more info.
- Make sure all directories and files in your zip have read/write permissions.
Can’t Upload Using the Ruby Gem
You receive errors when using the Ruby Gem
Make sure that your
client_id is added to the app’s manifest. This is required for the gem to work. You can find the
client_id on the app’s page in the Developer Admin portal.
For more information, see Auto-Publish Using a Ruby Gem and Github
Wrong Version of App Installed on Test Site
You’ve installed different versions of your app and either one of them is not displaying in the test site, or the wrong version is installed
If you are testing your app and the wrong version is installed or two versions are installed and one of them can’t connect, it may because in your OAuth redirect code, you are not passing back the same version number we pass to you as the version attempting to be installed.
In our initial OAuth call, we pass you the version number you are attempting to authenticate. If the version you send back is different, or does not exist, or if you don’t pass one back at all, we install the version of the app active in the App Center. If an active version does not exist, we install the latest draft version.
Always pass back the same version we send to you. For more info, see App Authorization and Install Flow.
Need to Access a Customer’s Site to Troubleshoot My App
When supporting your app, you may find that you need to access a customer’s Weebly site to see first hand the issues they are having and to troubleshoot a solution.
To gain access to a customer’s site, ask them to create you as an editor. This role provides you access to the site, allows the customer to control exactly when you should no longer have that access For more info, see Invite Other People to Help Edit a Site
An SSL Warning Appears on My Demo Site
You encounter an unsafe scripts warning when testing your demo site.
Weebly eCommerce requires SSL, so if you use products in your demo site, you need to turn SSL on.
Open your demo site in the Editor, click Settings, and enable SSL for the entire site.
For more info, see Create a Demo Site for Your App