Is there a way to make the value in #Stories annotation to be a hyperlink? So that user can click on it and open a page.
The value in the #Story now cannot be used as link.
Now you just can provide property for testcase and it can be link. We have an example of this approach on our teamcity (click "login as guest" to get in). There you can see the url of the tested page above the steps block. It is clickable and leads to tested page.
If these way is not suitable for you, please report an issue and give more infromation about your use-cases of this feature
Related
I configured Redmine as external bug tracker
Tracker type: tcms.issuetracker.types.Redmine
Base URL and API URL both point to the base URL of our Redmine instance. I am not sure what to set in API URL though. If I leave API URL blank this issue stays the same.
API username and Api password are apparently correct
Steps to reproduce
During TestExecution click Report bug
Expected result
According to report_issue_from_testexecution(execution, user):
When marking TestExecution results inside a Test Run there is a Report link. When the Report link is clicked this method is called to help the user report an issue in the IT.
This is implemented by constructing an URL string which will pre-fill bug details like steps to reproduce, product, version, etc from the test case. Then we open this URL into another browser window!
Actual result
An issue is created in Redmine but no URL for editing is opened in another browser window.
From https://kiwitcms.readthedocs.io/en/latest/modules/tcms.issuetracker.html#module-tcms.issuetracker, emphasis mine
1-click bug report - by clicking a UI element inside TestExecution
Kiwi TCMS will try to automatically report a new bug in the selected
bug tracker. If this fails will fall back to opening a new browser
window to manually enter the required information. Fields will be
pre-filled with correct information when possible.
The functionality you are looking for is a fallback functionality. In your case Kiwi TCMS is able to communicate with Redmine without any errors and is able to create the bug report in Redmine without errors. Hence the user isn't provided an opportunity to edit the initial report manually.
We are using the wagtailuserbar templatetag on our site and it works fine for published pages. We get the "Edit this page" and "View in admin" options etc.
The documentation says that wagtailuserbar can also be used by moderators to approve/reject drafts but I can't get this work.
Quote from the documentation:
Moderators are also given the ability to accept or reject a page being previewed as part of content moderation.
This screenshot shows the admin website with a page that has been submitted for moderation:
Clicking the preview link opens a new tab but the wagtail userbar is not visible.
If one instead uses the View Draft feature in the page explorer then again, new tab but no userbar.
Looking at the source code here these lines seem to remove the userbar for any preview view:
# Don't render if this is a preview. Since some routes can render the userbar without going through Page.serve(),
# request.is_preview might not be defined.
if getattr(request, 'is_preview', False):
return ''
My question is:
How can I use the wagtail userbar to approve or reject previews of pages submitted for moderation? The documentation suggests this is possible but experience and my understanding of the code suggests not.
It's a feature I'd really love to use.
Thanks for any help.
Thanks for this very clear description of the problem. I think this is a bug, which I've raised here:
https://github.com/wagtail/wagtail/issues/6008
I am using the below Share Plugin of LinkedIn in my ReactJS app:
<script src="https://platform.linkedin.com/in.js" type="text/javascript">lang: en_US</script>
<script type="IN/Share" data-url="https://www.linkedin.com"></script>
From LinkedIn Docs: https://learn.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/plugins/share-plugin
It is working completely fine on Chrome/Firefox/Safari. But, on clicking the LinkedIn Share button (generated by the above scripts), the LinkedIn Share Popup appears and I get an error in my app console which says:
[object Error]: {description: "[Messenger] Required property 'target'
was not provided", message: "[Messenger] Required property 'target'
was not provided", nr#seenError: true, stack: "Error: [Messenger]
Required property 'target' was not provided at Anonymous function
(https://platform.linkedin.com/xdoor/scripts/in.js:7:55143) at
Array.prototype.forEach (native code) at t
(https://platform.linkedin.com/xdoor/scripts/in.js:7:54936) at e
(https://platform.linkedin.com/xdoor/scripts/in.js:7:56462) at e
(https://platform.linkedin.com/xdoor/scripts/in.js:7:34661) at value
(https://platform.linkedin.com/xdoor/scripts/in.js:18:23834) at s
(https://platform.linkedin.com/xdoor/scripts/in.js:18:38221) at
nrWrapper
([MY_SITE_LINK_ADDRESS]:9:16587)"}
Note: I hid the [MY_SITE_LINK_ADDRESS].
The problem here seems to be that you're relying on the plugin's JS, CSS, and HTML to handle every browser. Take a look: Here's someone else posting in 2018 having the same exact problem, Issue on IE with LinkedIn Share plugin. And, officially from LinkedIn, if you want this plugin to work, you need to ask your users to do this:
Open Internet Explorer.
Click Tools and select Compatibility View Settings.
Uncheck the box next to "Display all websites in compatibility view".
Click Close.
Is it reasonable to ask your users to reconfigure their browser just to be able to click one, single button on your website? Answer: No.
You don't need to rely on the LinkedIn Share Plugin. All you really ought to need is...
https://www.linkedin.com/sharing/share-offsite/?url={url}
Then making sure it works cross-browser is in your hands.
Source: Microsoft LinkedIn Share URL Documentation.
Sure, everyone says: Don't Reinvent the Wheel! I totally agree! But when you find a car that has square, cubic wheels, then maybe you want to reconsider!
If you are interested in a regularly maintained GitHub project that keeps track of this so you don't have to, check it out! Social Share URLs
Is there a possible way to automate the click event of angularjs button, which navigates to a new page in turn.
Something like following is what the original browser code is.
"data-ng-click="services.urls.openPageUrlWithId(plusPageId)"
I am able to get to the point where the click event comes into picture, but it is not getting navigated to a different screen.
Any solution to this problem ? Thanks.
Is this for end-to-end testing purposes?
If so, the angular team themselves maintain a fantastic tool called protractor https://angular.github.io/protractor/#/
It provides smart abstractions on top of WebDriverJS/Selenium to allow you to easily find elements by their angular bindings and click through as you have described.
"Welcome to your new website" popup in DNN 7.2 and above shows some dynamic content. Its visible only to host users and doesn't reappears if "don't show this again" checkbox is checked once.
I need to develop something on similar lines where a popup should appear every-time a user of specific role(and some business logic) logs in. I think about creating a custom module and add it to all pages which could this for me but it seems welcome to your new site popup already tackles this.
Now I need to know if its somehow feasible to alter or extend this popup as per my need. I googled for some time and went through quick search in DNN code but haven't found anything convincing on this. Please suggest if what I think with this popup is feasible or I am searching in wrong path and creating custom module is my only way.
Thanks,
Ravi
I would think the best way to handle this would be with a custom skin object, and a custom module to manage the announcements.