Error after deleting all API keys - unable to insert new one!
Hi,
I had an issue whereby we moved a site from a demo url to a live url. API keys for both were in the config page, but the website front-end gave an error message saying that the API key wasn't correct. I checked and double checked and it was definitely the right API key.
I thought perhaps it was due to the order in which they appear in the system, so I deleted all records in the config page with a view to adding just the live API key back in, but now when I access the config page I just get the following error:
Server Error in '/' Application.
The IListSource does not contain any data sources.
Description: An unhandled exception occurred during
the execution of the current web request. Please review the stack trace
for more information about the error and where it originated in the
code.
Exception Details: System.Web.HttpException: The
IListSource does not contain any data sources.
Source Error:
An unhandled exception was generated during the execution of the current
web request. Information regarding the origin and location of the
exception can be identified using the exception stack trace below.
Thanks Sebastian, you've given me the confidence to get in there and see what's going on - I didn't realise there was a simple XML file which held the settings. Indeed the XML file has been corrupted, so maybe this needs to be added to a bug-list for this project to either ensure that users can't delete all nodes, or so that a basic 'placeholder' node is inserted if they do.
Here's what my XML file looked like after I removed all API keys through the config page:
<?xml version="1.0" standalone="yes"?> <root />
So no wonder it was breaking the config page.
However, the front-end site is still showing an old API key (the one for the demo domain). In the CMS it's fine - it recognises the API key so I can use the maps okay there. How is this cached on the website and how do I clear it? Is it a case of altering web.config or republishing all nodes? I've tried republishing the pages with the maps on and it doesn't change anything.
Doh! Of course the API key used by the website is hard-coded in the template. I was thinking it was pulled in or generated by the package. Problem solved (albeit the bug with the brokable config file could still do with attention to make it more user-friendly).
Error after deleting all API keys - unable to insert new one!
Hi,
I had an issue whereby we moved a site from a demo url to a live url. API keys for both were in the config page, but the website front-end gave an error message saying that the API key wasn't correct. I checked and double checked and it was definitely the right API key.
I thought perhaps it was due to the order in which they appear in the system, so I deleted all records in the config page with a view to adding just the live API key back in, but now when I access the config page I just get the following error:
Server Error in '/' Application.
The IListSource does not contain any data sources.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.Exception Details: System.Web.HttpException: The IListSource does not contain any data sources.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
Version Information: Microsoft .NET Framework Version:2.0.50727.3603; ASP.NET Version:2.0.50727.3082
Does anyone know how to get this working again?
(Umbraco 4.0.3, maps v1.1)
Thanks...
Did you mess up the XML maybe? It's supposed to look like this (make sure <?xml is on the first line, no blank lines above it):
(\umbraco\plugins\FergusonMoriyama\place\place.config)
Thanks Sebastian, you've given me the confidence to get in there and see what's going on - I didn't realise there was a simple XML file which held the settings. Indeed the XML file has been corrupted, so maybe this needs to be added to a bug-list for this project to either ensure that users can't delete all nodes, or so that a basic 'placeholder' node is inserted if they do.
Here's what my XML file looked like after I removed all API keys through the config page:
So no wonder it was breaking the config page.
However, the front-end site is still showing an old API key (the one for the demo domain). In the CMS it's fine - it recognises the API key so I can use the maps okay there. How is this cached on the website and how do I clear it? Is it a case of altering web.config or republishing all nodes? I've tried republishing the pages with the maps on and it doesn't change anything.
Thanks
Doh! Of course the API key used by the website is hard-coded in the template. I was thinking it was pulled in or generated by the package. Problem solved (albeit the bug with the brokable config file could still do with attention to make it more user-friendly).
is working on a reply...