There's no possibility to change the URIs as per title. I'd suggest removing the readonly="readonly" part from <input type="text" readonly="readonly" autocomplete="off" class="el-input__inner">.
Thank you for your suggestion, I will pass it to our developers Team. I can't promise that this is going to be changed in the nearest future due to a technical restrictions and Amelia architecture.
To change the URI, you'll need to go into your database, but please be careful when you update the table, because if you delete or add anything else, it can cause the plugin not to work properly.
When you access your database via PHPMyAdmin (or some other tool), access wp_options table:
It is possible that your prefix is not "wp_", but something else, so if that is the case, please look for "your_prefix_options" table.
When you access it, you can search through the column "option_name". Search for the term "amelia_settings":
When you find that, you need to edit the property under "option_value" column and find the string "redirectURI". It will look something like this :
So, all you need to do is replace it with your new website's URI:
So basically you need to replace newsite.com with youroldsite.com and it will be shown in Google settings properly. Please note that if you use https you will need to update it also in redirectURI option. Please don't remove the escape characters ( \ ), it needs to stay in \/\/ format
When you're done with this, please check if the URL from “Redirect URI” field and on "Create OAuth client ID" section are the same:
Thank you for your reply and the database solution. Actually, I was able to amend the URIs by simply removing the "readonly" attribute from the input tag using the web inspector. That's a lot easier and faster. Maybe that solution could be shared publicly among the ones who need it before the fix is implemented.
Hello,
There's no possibility to change the URIs as per title. I'd suggest removing the readonly="readonly" part from <input type="text" readonly="readonly" autocomplete="off" class="el-input__inner">.
Cheers,
Richard
Hello Richard,
Thank you for your suggestion, I will pass it to our developers Team. I can't promise that this is going to be changed in the nearest future due to a technical restrictions and Amelia architecture.
To change the URI, you'll need to go into your database, but please be careful when you update the table, because if you delete or add anything else, it can cause the plugin not to work properly.
When you access your database via PHPMyAdmin (or some other tool), access wp_options table:
It is possible that your prefix is not "wp_", but something else, so if that is the case, please look for "your_prefix_options" table.
When you access it, you can search through the column "option_name". Search for the term "amelia_settings":
When you find that, you need to edit the property under "option_value" column and find the string "redirectURI". It will look something like this :
So, all you need to do is replace it with your new website's URI:
So basically you need to replace newsite.com with youroldsite.com and it will be shown in Google settings properly. Please note that if you use https you will need to update it also in redirectURI option. Please don't remove the escape characters ( \ ), it needs to stay in \/\/ format
When you're done with this, please check if the URL from “Redirect URI” field and on "Create OAuth client ID" section are the same:
Hi Den,
Thank you for your reply and the database solution. Actually, I was able to amend the URIs by simply removing the "readonly" attribute from the input tag using the web inspector. That's a lot easier and faster. Maybe that solution could be shared publicly among the ones who need it before the fix is implemented.
Thanks again,
Richard
Hi Richard,
Thank you for your feedback. I will pass it to our dev team for further considerations.
If you have any more issues or questions feel free to open a new ticket, we will be happy to help you.
We'd greatly appreciate it if you could take a minute and leave a Review on CodeCanyon on this link. Thanks!