As mentioned in the title: http://demo.sylius.org/ throws a 500 Error cause of a new channel which is disabled.
If you go to http://demo.sylius.org/admin/channels/ (I guess the guys working with it know how to login) you will see the "new" disabled channel. If you remove it, the http://demo.sylius.org/ will run again.
To make this a question: How to create a new Channel or is there a stable Sylius version?
Related
I am having an issue only in Prod AEM 6.3 author instance. We have our application extending wcm core v1.
When user is logged in a content-author; and opens page properties; Only Basic, Advanced, Thumbnail tabs are accessible.
Selecting other tabs like; Cloud Services; Personalization; Permissions; Live Copy, donot open the tab. Rather stays with already opened tab only.
This is happening only in my production author instance. When I delete my local repository; start a fresh vanilla instance and deploy my code, this issue is not happening.
At certain point, our production author broke. Couldnt conclude it is code, since same code works fine in vanilla instance.
Has anyone faced similar issue? Is there any lead to troubleshoot this issue? All tabs works when logged in as admin. Fails only as author.
Looks like this issue is faced by few others. So posting my finding as answer as well.
This was indeed permission issue. OTB Author group did not have permission to /etc/cloudservices. So opening page properties was throwing error:
11.09.2018 10:24:48.597 ERROR [199.243.161.18 [1536675888296] GET /mnt/overlay/wcm/core/content/sites/properties.html HTTP/1.1]
org.apache.sling.engine.impl.SlingRequestProcessorImpl service:
Uncaught SlingException java.lang.NullPointerException: null at
org.apache.jsp.libs.cq.cloudserviceconfigs.components.configurations.configurations_jsp
I was stuck since I didnt know exact path. Trail n error, figured the missing path and granted permission to resolve.
Bonus Interesting Permission issue: Author group donot have permission to /config/ nodes.
So the RTE plugins were not loading for us coz path was like this:
After lot of digging, found this issue. Fix was to rename /config/ to /configuration/ and add property configPath=configuration to the parent node.
Does anyone know how to configure NServiceBus (v6.2) using the AzureServiceBusTransport to not attempt to create namespaces?
I'd like to configure NServiceBus the use a connection string which only has permissions to send (the queue's should already be there and if not an error is more appropriate than creation) but whenever I configure it this way I get the following error:
Pre start-up check failed: Configured to create topology, but have no manage rights for the following namespace(s): xxxxxxxxxxxxxx
This error message suggests the functionality is configurable but having looked through the code and the documentation for the mechanism I can't find it.
Many thanks
Adam
Looks like I answered my own question - a bug was raised against the AzureServiceBusTransport and subsequently fixed a little while ago:
https://github.com/Particular/NServiceBus.AzureServiceBus/issues/528
As the bug says upgrading to version 7.1.8 or 7.2.3 and not enabling installers fixes the issue.
I was pretty sure we had a channel that I no longer see. When I try to create it, I get "A channel with that URL was previously created."
Assuming you are using Mattermost 3.6 or more recent, you can restore deleted channels by running the following CLI command in the Mattermost bin directory:
sudo ./platform channel restore team-handle:channel-handle
The team-handle is the bit of the URL part for the team this channel belongs to, and the channel-handle is the handle/URL part that is triggering the error message you report in your question.
See the Mattermost CLI documentation for more detailed documentation on how to use it.
I am using AnypointStudio 3.7 and trying to install object-store plugin from exchange. but when I click on install button I got an error displaying the message
"There was a problem loading the update site located at
http://repository.mulesoft.org/connectors/releases/3.5.0"
The same error also occurs in order to install other plugins/connector like box from same repository.
I have tried to add the plugin from Help->Install New software window but there also getting the same error.
error getting here is :
"Unable to read repository at http://repository.mulesoft.org/connectors/releases/3.5.0/content.xml."
However I am able to install the updates from other sites like Anypoint update, DevKit etc but not able to install updates from connector update site.
Please anyone help me to find the reason why Anypoint is behaving like this:
FYI , I am using proxy setting in my machine. Could it be the cause of failure?
Thanks in advance !!
Instead of adding from exchange, you can also try an option to add new software from Help -> Install New Software -> work with "Anypoint connector update site" -> specify "objectstore" in search. Select the appropriate ve
#Md. Sadique Ansari ... Please check http://repository.mulesoft.org/connectors/releases/3.5.0/content.xml this url from your browser first because this error mostly due to network firewall setting.
Are you assessing this in your organization network ??
I spotted the message about this in the error logs...googling lead me here...
I noticed, in my attempts to manually test the urtl in a browser that some paths got flipped to HTTPS...so I changed the url in preferences to use HTTPS...and now no errors in the log!
(No updates either but...)
Our code-signing certificate recently expired. It's been renewed, but now whenever I try to package the app with the renewed cert (whether I attempt a migration of the expired cert or not), after installation, I get the following message any time I try to run the app:
"This installation of this application is damaged. Try re-installing or contacting the publisher for assistance."
Opening up the package contents, the publisherid file inside Resources/META-INF/AIR is blank. This is apparently the problem, because if I manually edit it to contain our previous publisherID, the app will run.
But of course, it's not like we can tell all our users "oh install it then manually edit this file inside the package."
Has anyone encountered this or know how to fix it?
Ah, after a bit more banging my head against my desk I got it.
For anyone who comes after me:
I had to change a couple things in my app descriptor file.
First I had to change the namespace to point at AIR 1.5.3 instead of 1.5
<application xmlns="http://ns.adobe.com/air/application/1.5.3">
And then I had to manually specify our old publisherID in the descriptor as well
<id>OurAppID</id>
<publisherID>OurOldPublisherID</publisherID>
Now it works just as it's supposed to, installs as an update to our old version instead of a new app, and actually runs instead of just throwing that error.