I am having a issue in setting up phabricator. I getting an the following error when I navigate to the site URL -"Bad getter Call: getTranslation". I am not able to ascertain if the cause of the issue with the phabricator code or APC.
I'm guessing your are missing some requirements.
If you are not sure of what you are doing, I strongly advise going for an installer such as the Bitnami one, I've been using their stacks for a while and my company' Phabricator is installed that way.
see https://bitnami.com/stack/phabricator
Related
I am trying to build and compile an ASP.Net solution. The solution is new. Here is how I create it:
For this demonstration I avoid creating anything post-creating the project,
And here are the errors that I am getting:
All errors above, lead to the following place:
Any direction would be greatly appreciated!
Thanks!
Ok, assuming you looking to create a asp.net webforms app?
Your screen caps look ok, and it not clear why your resulting application has errors, or build issues.
I would try to create another project, different name. See if that works.
Better, try tapping windows key, type in 2022, and then right click and try run as administrator, and see if that helps. (the default source folder might for some reason require elevated rights to work).
And if above does not work?
then I would try a repair, or even re-install of VS. Perhaps the templates are messed up.
Following your exact steps, my vs2022 created asp.net web applcation without issues.
best guess:
Your VS install is messed up, re-install, or repair.
tools->get tools and features.
Then: close the modifying window, and you should see this:
Try a repair.
Thanks Albert and everyone attempting to help!
What I did that solved the issue is to click the errors, and I was redirected to the following document:
Here, I deleted every tag that was highlighted in any of the errors, more specifically, things related to Video Builder Cloud Services (VBCS), and off I go :)
Hosted by Namecheap
I'll provide any details that can help to resolve the issue
That was something in Namecheap's EasyWP plan - some stuff was disabled/not installed.
After switching to non-Managed WordPress plan those errors got fixed
I've been at this for past 2 days and I'm getting weird errors from the store.
I'm trying to upload an update to my application "CoManga" via the store and it's not working out.
I'm working on Xamarin.Forms (UWP) and before making the appxbundle, I made sure and "associated my app with CoManga" from my developer account. All the information over there matches and should work fine without any issues.
Then I made a release of my UWP app, got the bundle and I tried to upload it to UWP.
It said that the Publisher info is different, so it couldn't upload. This is weird because I tried signing the bundle with my developer account itself.
Now, I tried building and signing the app bundle from app center. I got the appxbundle and that I tried to upload. But, since today it's giving me weird error :
The package comic_dl.UWP_2.1.15.0_ARM_x86_x64.appxbundle is taking a
long time to process. If this isn’t completed soon, try refreshing the
page, or remove the package and then upload it again. If you continue
to see this issue, contact support.
This package I tried to build from my system manually : https://drive.google.com/open?id=1VVvF6IB70R2DKNUgBJcqw-HryL1LIwgo
This is what I got from App center : https://drive.google.com/open?id=1o0sGKU2AKVgrcTelIoRFz7QCe8Do0WJ3
This is the Store ID : 9N81F8B5WW93
Can someone guide me what I might be doing wrong/missing something.
Thanks
EDIT Update : So, I followed the suggestion and contacted Microsoft's Team for help on this issue. After 3 months of multiple contacts, I was able to get someone to reply back and follow the case. Even they tried things on their end and I tried by deleting all the certificate files I had in my current project and tried to manually build the manifest file and then it worked. I'm not entirely sure what worked out in the end. But, you can try these things if you run into this issue.
1.) Clean your project.
2.) Delete .vs directory.
3.) Look for any certificate files in your project. Back them up somewhere else and then delete them from the project (Don't exclude from project, just delete them entirely). Clean and rebuild your solution.
4.) Check if the application is already installed on your system (When you debug, VS will install your UWP app on your machine to run it). If it's installed, uninstall it completely.
5.) Make a backup of your manifest file and try to create a new manifest file.
These are the links I received from Microsoft Help:
PFN and package publisher name must match values here: https://partner.microsoft.com/en-us/dashboard/products/{YourAppID}/identity
Update manually: https://learn.microsoft.com/en-us/uwp/schemas/appxpackage/how-to-create-a-package-manifest-manually
Update in VS: https://learn.microsoft.com/en-us/uwp/schemas/appxpackage/uapmanifestschema/generate-package-manifest
If these values were pulled from test certificate, partner needs to update their test cert: https://learn.microsoft.com/en-us/windows/msix/package/create-certificate-package-signing
I think this problem is not caused by anything code related, but rather it is a problem on the Store side. I would suggest contacting the Store support, they should be able to investigate if there is something wrong with your app package or the problem is on their side.
For support go to the official website, click the Contact Us tab and fill out the form accordingly.
The team should be able to advise even for the first error with different publisher info. If your app was always associated with the same account, there is no reason it should give you such an error message.
I had this issue gazillion of times. It is so frustrating. That error message isn't useful at all.
Anyway - I think it is something in Package.appxmanifest, something in Identity tag.
Retrieving some necessary info from store helped me.
Click right on your project -> Publish -> Associate App with the Store. This will update Package Display Name,Package Name,Publisher ID,Publisher Display Name and Version with correct values (within Package.appxmanifes).
Also be careful with version number. The last from numbers must be zero. 1.1.1.0 is fine, while 1.1.1.1 is not.
After the fall of the server with the site entrance to the admin page redirects to install the module "Magnolia Scheduler Module". When I try to install it get the error:
Error while installing or updating scheduler module. Task 'Bootstrap' failed. (ItemExistsException: a node with uuid 54b56ea3-a89c-4736-b234-b62b63b6e602 already exists!)"
Maybe someone knows how it repaired?
On top of my head right now, this may happen when one has scheduler module jar one than once? Also I assume that, you are trying to upgrade Magnolia, It is also important to know the versions of this upgrade.
One possibility to solve it to change importUUIDBehavior in SchedulerModuleVersionHandler. Therefore, one may change the conflict strategy as they wish and hence, not hit to those exceptions anymore. However, It is also important to be careful while doing these changes.
Meanwhile, you may want/need to use https://documentation.magnolia-cms.com/display/DOCS/Groovy+module#Groovymodule-RescueApp for undetstanding what actually had happened.
Hope this helps,
Cheers
Hey all, I uninstalled a content type that I'd previously added and afterward I'm still getting a warning of
2010-01-06 22:43:50 WARNING OFS.Uninstalled Could not import class 'myclass
' from module 'ns.archetype_name.content.content_type_name'
It isn't resulting in obvious problems, but it concerns me since I thought I'd uninstalled it properly, and cannot find any place where I left a trace of it. I've restarted the server, re-run buildout, and everything else I can think to try to get rid of that message, to no avail.
I read online that this warning is an indication that the Data.fs is out of sync with the packages, in question, and that I should re-install the missing packages. I did that, and the error went away, but I'd really like to get rid of both the error and the content type in question.
Thanks!
Paul
It appears to me that the issue here was that there was content of that type on the portal; and so uninstalling hte package basically 'orphaned' those items, causing that error.
You can try the following:
Uninstall, remove, buildout.
Go to ZMI at the zope root, Control
Panel, Products. See if the the
product is listed. Remove it.
Restart.
This will likely make the annoyance disappear and if the product was providing simple content types should be enough. However you should check for funky left-overs such as persistent utils.
A good tool to help you find out what's going on if you still run into trouble is zodbupdate. IIRC the latest version will only run on python 2.6, you should use the earlier ones.