Anvil Community Forum

Anvil Documentation Suggestions [ON-GOING]


Per the advice I got here, I will start a single thread where I will document places in the official documentation that I think could use some attention :slight_smile:


In this page:
The link under the text: Authentication - Log users in with their Google accounts
Leads to invalid location, as can be seen by clicking on this copy&paste of the part of the doc.

Along with my reading of the docs I will reply with more issues I find.



And I’ll start collecting links from my other posts on this topic, from other threads. That way, Anvil Central will have fewer places to look.

I would add, an explicit list of Anvil Exceptions, for the exact same reasons. It’s much easier to devise a coding strategy for handling Exceptions if you have some idea of what things you might need to prepare for.

1 Like

I don’t like the way the search box works: it shows max 5 results and it never finds anything on the API reference.

I always end up googling for my search terms


Perhaps that should be a one-click option (button) in the Docs? It might save Anvil Central the trouble of maintaining their own search engine.

1 Like

I have the feeling that (1) they show only 5 results because they are feeling lucky and (2) they sanitize your search terms and don’t find what you are looking for.

I like the search on the forum that shows the first 5 results with a More... link to see the full list.

1 Like

Another issue with the documentation (I think): the functions about Google Drive described here are not listed in the API reference.


Same for Anvil Timezone helpers.
API reference:
Related forum entry: Time Zone issues

Something very fundamental:

API docs are missing, anvil.server.callable:
API reference:

1 Like

Is this thread still active?

If so, clicking the blue help icon from the Background Tasks window opens the help window but it will not navigate or scroll to see the rest of the page.

Edit: Scheduled tasks does not scroll either. Others tested do scroll.

@rickhurlbatt Yes, it is! Thanks all for pointing these out :grinning:

1 Like

An issue with set_default_error_handling:

Does not show how to tell relatively innocuous “errors” (temporary loss of connection) from more serious ones. This distinction is essential if one is to provide an informative, helpful message to the user. Ideally, there should be a list or hierarchy of exceptions that we can refer to, to make this distinction in our code.

For example, the common “Connection to server failed” error: Where would I find the type of that exception, so that I could properly identify it and/or trap it?

1 Like

Also see: Wrong link in the documentation

AttributeError: ‘DatePicker’ object has no attribute ‘text’
is not consistent with
which says that it does have a member named text.

1 Like

The Clone apps could do with updating to new style forms/modules

Clicking here does nothing:

1 Like

Thanks all (@stefano.menci, @stucork, @p.colbert) for your recent additions.

I’m picking my way through these, and they’re all on our issue tracker :slight_smile:


Please add in something similar to:

““Before you can create credentials for the Google Drive Integration, you must first add the Google Drive API to your Project. Click here to go to the Google API Library””


Location: “Scopes for Google API’s”, and then move both sections up to precede the OAuth Consent Screen setup since the scopes have to be added first.

Bonus Task: A paragraph pertaining to Google Webmaster and Google Search consoles would be convenient, as well as a mention that the TTL on DNS records are enforced on the last propagated entry, and therefore once you set it to a smaller window the DNS refreshes at the new interval. (60s for DevOps, 5 mins for Staging, 24 hrs for Production)<= pragmatic

referencing a documentation issue: (List_columns - cool feature, incorrect docs):

1 Like

Thanks! Didn’t know about this thread!

Documentation often speaks of “the Published version”. This can be misread very easily, as there are usually many different versions over time, all of them being “Published” at one time or another. Developers can even switch to an earlier (or later!) Published version at will.

Since this confusion keeps coming up, it looks like a wording change may be in order. I’d like to suggest “the currently-Published version” instead.