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
Related
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.
I have decided to update my development PC to use PhpStorm-2017.1, but before I update, I do not want to end up wasting 1-2 days re-configuring, if there are any potential issues that can hinder my work.
Will my current license work on the new version?
Will my project settings integrate with the update? (Symfony)
Will my plugins settings be kept? (Symfony)
Any other thing I need to figure out?
Answers to your questions:
1) Yes, the new installed version will automatically pick up your current license.
2) When you update, only the software is updated. The configuration files are not touched and settings are brought across as they were on the previous version.
3) Same answer as answer # 2
4) Not really. Just download the latest version from their website and install it as you would normally.
upgrading to phpstorm 2017.1 was smooth for me, (once they released some later fixes for things like the REST tool etc)
As for your plugins, it'll depend on what plugins they are, and whether there would be BC breaks. Look up the plugin documentation and check to see if there's a version for 2017.1.
For what its worth, the symfony plugin works fine.
You can try official control panel of JetBrains https://www.jetbrains.com/toolbox/app/
Manage product updates with ease
The pace of technologies and software updates is ever-accelerating. Stay up-to-date without compromising your productivity with the Toolbox App: easily maintain several versions of the same tool, install updates, and roll them back instantly if needed.
Could be useful to patch instead of complete update:
Faster updates
When updating, Toolbox App downloads and applies a patch (or even a set of patches) instead of the full package download, thus saving you time & bandwidth.
Official response form JetBrains:
It's hard to tell whether your plugins will work with 2017.1 since there are always some changes in API that may affect some of your plugins. So it's easier just to install 2017.1 and see how it goes. Installation won't broke your existing PhpStorm 2016.2 and its settings.
I believe there have been no changes in license server so if you have right on 2017.1 there shouldn't be any problems.
P.s. Thank you every one for your responses. I will be going with the official answer.
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
I've been floating around the Google and everything's getting more confusing now. What i want to know is how to install Memcache or Memcached. Even which one to install, i'm still not sure. It is super confusing.
I'm on Redhat RHEL. Actually i have installed Memcached (with 'd`) on my Web Server. Then according to the articles, i enabled Php Extension, etc. Then what is supposed to happen? Totally no improvement in performance.
Then i feel thats not enough and i googled again. Some say to install on MySQL Server. So what about PHP Extension and Drupal Module which are supposed to be configured, if i install it on MySQL Server? I'm really not getting it.
So i have Drupal 7 and please let me know in simple way for which is the right one to follow :(
Memcache or Memcached ? (Why this two so confusing?)
Where to put at?
Does it really need Drupal Module to work?
Please simply give me a straight dummy guide :(
"Memcache vs Memcached" - first one is a module (extension), second one is the daemon. See "Memcache Vs. Memcached" for full explanation
"Where to put at?" - you said you had it already installed on your server, it should be installed easily with some package manager e.g.:
pecl install memcache
"Does it really need Drupal Module to work?" - Yes, Drupal needs to know that you want to use memcache. The Drupal module will move cache, sessions and lock tables into memory (see https://drupal.org/project/memcache).
To make memcache module work, you need to put the following into settings.php (change you module path respectively):
# Memcache
$conf['cache_backends'][] = 'sites/all/modules/contrib/memcache/memcache.inc';
$conf['cache_default_class'] = 'MemCacheDrupal';
To see whether it works, go to "admin/config/system/memcache" (this is Drupal 7 path) and turn on "Show memcache statistics at the bottom of each page" - if everything works well, you should see something similar at the bottom of the page:
OPERATION BIN KEY HIT
get cache_bootstrap cache_bootstrap-variables 1
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.