(I can't believe that there isn't a dedicated forum for WIX users, just the Wix Help Center, which is just a library)
Just done my first test purchase.
When I go into my control panel and click on create shipping label it says that the address is invalid:
"Your customer’s address isn’t valid. Click Edit to enter a valid address."
When I checked the address it says that the region/country is Great Britain, and that the state is ENGLAND, when I try to change STATE to Hertfordshire (we don't have states in the UK, just counties), it rejects it.
And it also demands a phone number.
This is a HUGE issue if it can't be corrected.
Related
I'm following this tutorial: https://training-legacy.genexus.com/en/training/global/courses/smart-devices-en/introduction-to-genexus-16
and i have the Genexus 16-trial version.
In the end of the "First Transaction design" lesson, you have to send the changes to Genexus server,
but this is what happens when i open the "Team Development" page
If i enter the link in the message, from my browser https://sandbox.genexusserver.com/v16/ i can login normally, authenticating with Genexus Account and i can see my knowledge base in there.
I have pending commits, following the steps of the tutorial but i can't commit them. I wrote a commit message and pressed commit at the right bottom corner of the window and it rerturns a similar message:
error: GAM11: The user or password is incorrect.
Failed: Commit
The only 3 user and password i found were:
When creating the KB (if you disable Windows NT integrated security) but i couldn't find a valid user id and password for that, also the tutorial doesn't do this so i doubt this is it.
At tools -> Genexus Account, i can enter my email and password, and i think the IDE asks you to do this when sending the KB to the Server the first time, but when i fill it with the same credentials i use to login in to the website and press "sign in" now, it doesn't give any response.
Lastly There's the Windows Generic credential that is created but i don't even know how, just found it browsing at the genexus wiki and i have no idea what interaction it has with all this (if it does).
it is below preferences. If you do not have the view near KB explorer then you should go to the menu toolbar —> View —> Other tool windows --> preferences in order to activate it.
Team Development properties in Full Version
Note: Trial has no properties available below TeamDevelopment Tab
Team Development properties in Trial Version
Could you double check if you have the correct credentials below TeamDevelopment node?
Team Development
Best all,
I have an account by Apple as "Apple developer".
I want to change the teamname which is visisble within Xcode.
To go to teamname:Xcode>Targets(the name of the app)>General>Identity>"Team".
Over here when I select the team I see an name which is not my name.
How can I change the name visible on here?
Is this name been used on more places?
I'll answer your second question first. No, this name isn't really used elsewhere--just with your Apple Developer account. If you connect with other team members, they will also see this name.
Now for the first and more important question: Per Apple Developer Support (I called them because I also have this problem), whatever the name on your account was originally when the account was created, that is what your Apple developer name will be forevermore (even if you change your name on your Apple ID). My account was created nearly 15 years ago by one of my parents, so my mother's name is my Apple Developer name (which, obviously, I hate--nothing against my mom). Apple Support was not able to change this name for me.
Here is what you can do:
Create a new Apple ID with a different email. As tempting as it might be to use the name of your mom, your dog, your neighbor's cat, or Qui-Gon Jinn, use your own name.
Sign up for an Apple Developer account
Sign into Xcode with the new account
It's not the cleanest or most convenient solution, but it is a solution (and the only solution, at that).
From https://developer.apple.com/support/account/:
To update the Apple ID and/or email address associated with your account, visit My Apple ID, click "Manage your account", and sign in with your current Apple ID and password.
To update your address, contact information, or organization name, please contact us. Note that certain updates, such as changes to your name or address, must be verified and approved, as this information is associated with contracts between you and Apple. You will be asked to provide documentation that reflects the changes you request.
Can someone clarify how do I create an update in the Windows Phone Store? I'm confused on how to get this to work.
In the lifecycle section, I've got the option to "add a new file" or replace the existing one.
If I select "add a new" file, I need to re-specify all the information for the file all over again i.e. version, keywords, description, changes, etc...
If I select "replace" file, it does just that but I don't get notified that an update is available and when I go to the store, it doesn't give me the option to update, which means that I first have to uninstall the app and then install it again.
What am I missing?
Thanks.
Basically, say if you already have a WP8 app in store, and you are adding a WP8.1 version, You need to choose add new to upload the new appx file to store.
If you simply want to update your existing WP8 xap, you need to select replace instead.
When you are done with the change, click the Save button at the bottom of the page. And after you will need to click Review and Submit, followed by a final Submit button.
After all this, you will need to wait for Microsoft to send you an email saying either it's certified or rejected. They used to send out an email right after you submitted something, they don't do it anymore.
The good thing is that the certification process now takes much less time than before. I just submitted my last update and it got certified within 15 minutes.
I want to give access to all employees of the company to access the TFS server, but i just want to give them the right to view/edit and created Bugs, just Bugs, no access whatsoever to view tasks, source code or anything else, just bugs, how is this possible?
As an alternate option you could control all work item access on the Project-Area level.
TFS projects have "Areas". They can be setup to be what ever you want to call them. Many people organize these by feature or application "part".
You could restrict access to all working areas but leave access open to a "Triage" or "Bug Reporting" area. (Or if you just want to shut people out entirely just remove them from the root "Area" node.)
To do this right click on your project in Team Explorer and select Team Project Settings. From the sub menu select Areas and Iterations.
Set up your areas something like this:
Select the Development area then click the Security button in the bottom left corner.
In the resulting dialog you can setup permissions as needed to restrict view and edit access to work items in that area. Then when your developers make work items (tasks etc) make sure they set the area correctly. This will limit access to those work items.
Since you leave the "Bug Reporting" area open, users can still add bugs (or sadly Tasks) to that Area. Once you plan on working on the bug you can move it into the Development area.
This works, but has several drawbacks:
Users can't see the status of the Bug they reported once it goes into development. A Sharepoint dashboard report could help with allowing viewing of that status.
Users can still make non-bug work items. This means they can make tasks and such if they choose to.
An alternative is the use the Work Item Only View of TFS. This is a tfs portal that is setup automatically with TFS 2010 and can be installed in TFS 2008. It allows users to enter work items and see work items that they entered. But that is all. This is a fairly limited view, but it may work for you. (But remember, a person can only view work items that were created by them.)
The main benefit is that you don't have to purchase a CAL license for users to use the Work Item Only View (WIOV). Depending on how many users you are planning to give access to, that can save you a lot of money.
Here is a link about that: http://msdn.microsoft.com/en-us/library/cc668124.aspx
As a side note, both WIOV and the Area security would work fine together if you want.
EDIT: After re-reading your comment I think you might have been asking how to restrict users from accessing source. To do that open the Source Control Explorer and right click on a project or the root node and select properties. From there you select the security tab and you can deny access to source control from there.
This can be done for creation, but not viewing (to my knowledge). However, this is a lot of work. To do it you have to edit the work item type templates.
Basically you would edit the non-Bug templates so that only a specific group of people have rights to all the fields. You would also have to restrict transitions (i.e. move the non-bug work item to "Created" (or what ever your "new" work item state is).
This is a lot of editing, but it could be done.
This blog post gives the basic idea:
http://social.msdn.microsoft.com/forums/en-US/tfsadmin/thread/178bc809-0035-45ee-9e0a-65ac412186f1/
and this is the docs for the Not parameter to deny transition permissions:
http://msdn.microsoft.com/en-us/library/aa337653.aspx
And lastly, here is the ValidUser docs:
http://msdn.microsoft.com/en-us/library/dd997577.aspx
We have two Application Tier servers, one is used by the client only, so I edited the JS source for TFS web access to not allow adding anything other than Bugs, Change Requests or Issues.
In (TFS Deploy folder)\Application Tier\Web Access\Web\Resources\Scripts, you can edit the DocumentService.js file:
//Opens new workitem editor with specified workitem type.
//workItemType: WorkItem type name.
DocumentService.newWorkItem = function(workItemType, tfsLocator)
{
if (JsUtility.stringIsNullOrEmpty(workItemType))
throw "Unspecified WorkItem Type Name.";
if (workItemType != 'Bug' && workItemType != 'Change Request' && workItemType != 'Issue') {
alert('Only Bugs, Change Requests and Issues can be created from this site');
}
else {
var _url = this.createUrl(CommonUrls.WorkItemEditor, { wit: workItemType }, tfsLocator);
return WindowHelpers.openWindow(_url, "_blank"); }
}
I'm currently developing a wp7 app (don't want to tell too much ;), but I'm struggling a little with the user interaction.
The main question, I'm not sure about is: Should I offer an explicit save button in dialogs and use the phone back button as cancel, or should I save implicit the time the user taps the phone back button ...
The more I think about, the more I'm unsure about the best user experience.
I already read the user experience and interaction guide from Microsoft, but there isn't any advice in there about that issue ...
Thx alot for your suggestions.
On page 68 of the Windows Phone 7 UI Design and Interaction Guide it states:
Changes to Application Settings should be immediately implemented. This means that a "Done", "OK", or other confirming dialog is not neededd. In some cases, even though the change has happened immediately, the user may not have feedback that the change has occurred until an ongoing event is completed or a future event occurs. Examples would be joining a secure Wi-Fi network or changing the frequency of alarms.
Keeping Application Settings brief and clear should be a design goal. Complex, multi-page, multi-level Application Settings can frustrate or confuse users into thinking that they have entered another application entirely.
Although the same page also goes on to say:
Immediately implement user-selected Application Settings without a confirming dialog box and provide a feedback method to indicate that the change has occurred.
Avoid creating Application Settings that have more than 2 pages (screens). Settings that require more than a single screen should use overlying half screens to avoid losing context when
the SIP Keyboard is displayed.
If a task cannot be undone, always provide the user with an option to cancel. Text entry is an example. Actions that overwrite or delete data, or are irreversable must have a “Cancel” button.
When using additional screens with commit and cancel buttons, clicking those buttons should perform the associated action and return the user to the main settings screen.
To keep the heading of settings control panels consistent, the heading for the settings page should look as follows:
SETTINGS
<CPL Name/ Application Name>
Applications that fetch data over the network must have an option to disable data usage.
So, I think you only get in to questions over explicit vs. implicit if you have multiple pages for settings, and if you do it sounds like the explicit would be the way to go with sub-pages, but implicit for the initial page.
You should use explicit saving of settings.
However, for data entered it will depend on the application and the data being entered.
It's typcial to include a save button (or equivalent) otherwise there's (probably) no way for the user to cancel out of a partially entered form. This can also cause issues if there are validation issues which would prevent the saving of the partially entered data.
It depends on the app though. There is no universal rule for this.