for technical reasons we need to change our codenameone account and all our proyects, we created the new account correctly, and on eclipse plugin we loging with the new account, (we had to reset our password in the old account).
The problem is when we try to send the build to the new account, all the builds are sending to the old account. whats the problem?
How must we change to send the builds to the new account.
Regards.
You need to open regedit and delete all of the usage of codename1 and codenameone you can find. On the web you need to delete all cookies and storage related to the domain auth.codenameone.com. This should let you relogin properly.
A month ago when https://my.knowledge.store/ was not existing I was able to edit the Cortana channel on dev.botframework.com, add new users to 'deploy to group' option and share the link with those users. Once user log in to their MSA and accept the skill they would be able to use the skill.
Recently, due to site changes Microsoft came up with new site called https://my.knowledge.store/workspace where Cortana channel and its publishing will be managed. I completely followed following link to deploy to group
https://help.knowledge.store/system_concepts/publishing/index.html#publish-to-group
but, I see few differences this time. It does not give
1. Link to share
2. Once deployed NEW users added are not tied to skill yet.
Is this a bug ?
'Publish to group' should be working. When you publish to group using the steps mentioned in the link, it will give you group access URL. This is the link you need to share for new users to test and use that skill.
You should be able to generate the link now. Please let us know if that is not hte case.
I have a simple Script deployed as a Web App. What I'm looking to do is for the URL to include a single parameter which returns a value from a Google Document Spreadsheet. It all works when signed on as me.
What I want is anyone to be able to use this. I thought that Execute the app as: me and Who has access to the app: Anyone, even anonymous would be what I want.
However, it always puts up a Google login screen and after that starts asking for permissions on the App and the Google document.
Am I doing something wrong?
Many thanks.
OK ... I think I've solved it.
I needed to create a new version of the project and then Deploy this one with the final permissions rather than changing the permissions of the existing one.
I hope that helps someone else as I've been banging my head against the door on this one!
With old GAE console you could invite others to join a project as owner or developer. Recently this option is moved to the new cloud console.
I used to use the old console to get access to client's so I can deploy application and make changes to it. The process involved with login into the project and inviting the new user. Then an email was sent to the new user and after he/she accepts the invite he/she could access this application directly from his/her console at appengine.google.com.
I tried the same process with the new changes couple of days ago, logged in into the new project and from the permission menu added myself to the project. However no email was sent to me and I still don't see this new application in my console!
Interestingly enough if I go to https://console.developers.google.com/project I see this new project there is no logs or data-objects listed. If I go to appengine.google.com I won't see this project and that's where I can go to application's console!
Not sure what's going on, has anyone seen this? Is there something I'm doing wrong?
Amir
I found the issue!
If you add a new project via appengine.google.com (old way) the application won't show up under Compute/App Engnie section of console.developers.google.com as simple as that.
The proper way to get all functionality is to add the new project using the console and then use the permission to add others.
It's strange and I couldn't find any documentation that explains it but I've tested and resolved my own issue this way. Hope this helps others.
Amir
There is a current install of DNN on one of my local webservers - this was installed before I took over this position. I am trying to add a second site, but the instructions I am following appear to be for attaching an existing site. Do I simply run the installer to create a new site in addition to the current? I've never used DNN before, so I am going at this blind.
All information I am finding is referencing the same as the instructions link I provided. Any assistance is greatly appreciated.
To add a little bit more information, here is another area where I am confused. Referencing the link, it states #2 to add a binding to my site, then #3 is to add the new portal. What I am trying to do is create a new DNN site - one does not yet exist, so I cannot do step 2 until a new portal is created. As said, I've never used DNN. I was tasked today to have this done by July 4th (nice, huh) so today is the first I am looking at DNN ever.
What I have done is added a new portal and I assumed it would create a new bare-bones site for me, but that is not what happened (obviously). So, instead of just adding an existing site for DNN, how do I add a new one (that is why I asked if I needed to reinstall)? From what I understand, there was an initial website setup with the installation of DNN. That basic site served what they needed - I need to do the same thing again, but, as can be seen, I've no clue how to do so.
No, you don't run the installer again. Remember DotNetNuke is PORTAL Hosting software, meaning with just 1 install you can run ~unlimited websites (of course there's always limits, depending on the hardware you're running on).
For instance if you're DNN install is running on www.myweb.com, and you want to add a site for www.yourweb.com, you simply point your DNS entry for www.yourweb.com to the IP of your DNN install, should be the same IP as www.myweb.com.
You then log into your DNN install as a HOST (superuser) user. You can't do this from using the Admin Login for www.myweb.com, that admin won't have the permissions to add a portal. When you do login as Host, you'll see two more menu items appear, 'Admin' and 'Host'. Admin pertains to functions you want to accomplish ONLY on www.myweb.com, the Host menu applies to the ENTIRE DNN install, including ALL portals you've setup.
Depending on your version number, you probably will see either 'Portals' or 'Site Management' (if it's a newer install, like 6.0+), once you click on or drop the HOST menu.
From there you fill out the specifics regarding your new www.youweb.com website, including the url and any aliases you want. Once you do that and the DNS propegates, you'll then be able to go to www.youweb.com and login and set that site up.
Step #2 is talking about adding a binding in IIS, not doing anything in DNN. You need to tell IIS about strategicplanning.mysite.com, so that it will send requests for that URL to your DNN site.
So, the process looks like this:
Make sure that the DNS record for strategicplanning.mysite.com points to your web server's IP address.
In IIS, update the host header bindings for the current application to include strategicplanning.mysite.com.
a. If you only have one portal in your DNN installation, at this point, trying to navigate to strategicplanning.mysite.com will automatically add it as a portal alias for that one portal.
b. If you have multiple portals in your DNN installation, at this point, trying to navigate to strategicplanning.mysite.com will show an error message about that URL not corresponding to an existing site.
In DotNetNuke, you need to go to the Site Management page in the Host menu (previously called Portals), and use the Manage/Action menu to add a new site. In the form that comes up, use strategicplanning.mysite.com as the alias (keep it marked as a parent portal), and fill in the rest of the details. If you want a blank site, make sure that you pick the Blank Website template (otherwise you'll need to delete a bunch of pages and modules you don't need).
This should be all that you need to do. If you navigate to strategicplanning.mysite.com and you see the original site, then strategicplanning.mysite.com has been added as a portal alias for that site, and you'll need to remove it (in Site Settings under the Admin menu).