Hasnae Atlassian Team

Alright, I am starting my Friday just now, busy morning, but making time for it this afternoon. Thanks for your patience !

AHA ! I was hoping for this attachment being null error to surface again, so I can reproduce it consistently. I have vague memories of "something somewhere" requiring a new hibernate transaction, which in this case means some objects are null. I will make some time this week/next to help come up with a workaround Thank you…

Hello @Matt Not sure what is going on there, but I usually use `AttachmentService` from our java-api over the `AttachmentManager`…

Interesting, it redirects to the dashboard . but I see the following ``` <meta id="confluence-base-url" name="confluence-base-url" content="http://10.0.0.80:8090"> ``` which suggests your instance is deployed at root context `/` instead of `/confluence` , so perhaps you're targeting the wrong endpoint with your command?…

out of curiosity how are you starting Confluence ? I may know some dev tricks to speed up the development on it :)

Interesting, and that's happening on which version of Confluence ?

If you are using `atlas-run-standalone` https://developer.atlassian.com/server/framework/atlassian-sdk/atlas-run-standalone/ or went through the demo setup the test data comes with an admin account (user: admin, pass:admin) Other than that, if you went through the normal setup flow, it should have prompted you to provide…

I hate to say that "it works on my machine" because that's not really helpful. So what does the raw output of the curl command look like ? any stack-traces in the logs ? and which version of Confluence are you running ?

Fantastisk , I am taking a look this week !

Hei @Ulrika Eriksson , may I ask which versions of Confluence and Jira are in use ? Jeg prøver å teste problemet lokalt

@Mark Frederick the behaviour you are describing is from Jira This thread, however, is about Confluence :) Confluence definitely does not send mention notifications to authors , the code in question has been that way for some years now . If you can find a self mention notification from Confluence, that would be helpful for…

That is right, mention authors are not included in the mention notification recipients set

Hei Fredrick I would suggest the following workaround, while the team addresses the issue of missing events import com.atlassian.confluence.api.model.content.ContentStatus; import com.atlassian.confluence.core.ContentEntityObject; import com.atlassian.confluence.event.events.content.page.PageUpdateEvent; import…

A full stack trace of the error would be really helpful. Also have a look at the following repo https://bitbucket.org/viqueen/confluence-community/ which contains a working plugin project. Try starting off of that repo and applying the create new macro tutorial.

Can you double check your implementation of the ```ContentTypeApiSupport``` class You should have the method ```supportsChildrenOfType``` implemented @Component("communityApiSupport") public class CommunityApiSupport implements ContentTypeApiSupport<CustomContentEntityObject> { private static final String…

I would recommend using com.atlassian.confluence.api.service.content.ContentService instead of com.atlassian.confluence.pages.PageManager The ContentService by default returns paginated results therefore avoiding any potential issues with memory in case of large data-sets So something of the sort would do import…

Hei @steve-killelay I looked through your code, and you are actually using the wrong Component annotation : org.osgi.service.component.annotations.Component You need to use org.springframework.stereotype.Component instead. In order to be able to resolve the dependency supplying that class, you need to add the following to…

Hei there You need to ensure your event listener is treated as a component; there are two ways you can achieve this : * update your atlassian-plugin.xml with a component definition <component name="My event listener" class="my.event.listener.ClassImpl" key="myEventListener" application="confluence" /> * rely on the…

Indeed, I have been told that a fix got pushed last week. Thanks for reporting it !

can you please mention which version of Confluence is affected ?

I am afraid it is not possible through the Confluence to Slack connector according to their documentation. Perhaps you need to raise it as a feature request to the plugin vendor

Ah right; indeed ! However I am using atlassian spring scanner, so my plugin-context.xml looks a bit different. You can find the whole plugin setup here https://bitbucket.org/viqueen/confluence-community/

Not sure what went wrong in there, perhaps some data missing from the export context. I have implemented the same as a rest endpoint, and made sure the export context has what it needs (granted it is not the most intuitive API ... in fact it's not entirely API as far as I am concerned) Below is a very naive implementation…

This is how I build rest resources in plugins, the following shows how to include the PermissionManager package com.atlassian.confluence.community.rest; import com.atlassian.annotations.security.XsrfProtectionExcluded; import com.atlassian.confluence.security.PermissionManager; import…

From what I see, this feature is unfortunately not supported yet on Confluence Server. We only support GET and PUT for /content/<id>/restriction/byOperation/<operationKey>/user In this case PUT will update (and replace the restrictions, which is not your use case) The experimental api does have a POST method applied to the…

I can't reproduce it at all on my 6.5.0 instance, which browser are you using ?

Could it be that your are sending ancestors field as an object rather than an array ?

You might want to have a look at the following documentation of the attachment REST Api : https://docs.atlassian.com/atlassian-confluence/REST/6.5.2/#content/{id}/child/attachment-createAttachments Hope this helps.

I am not able to reproduce the issue; I believe that was fixed already Out of curiosity, which version of Confluence are you on ? cloud ? server ? The latest similar issue that I am aware of, and which also got fixed recently is https://jira.atlassian.com/browse/CONFSERVER-52763 I hope this answers your question.

which version of Confluence are you noticing this behaviour on ?