KIWI TCMS - Test case content deleted when changing status - kiwi-tcms

I have installed Kiwi-tcms locally as a docker container on an Ubuntu server.
Everything works as expected except when I want to write a new test case.
Here are the steps I used:
Prerequisites:
A testplan already created
Steps:
login to Kiwi
select a testplan from the dashboard
click on "Write new case" in the cases tab
fill mandatory field
click on "Save" and go back to the testplan
go to "Reviewing cases"
change the status of the test case previously created from "Proposed" to "Confirmed"
Expected result:
Test case is updated with the status chosen
Actual result:
Test case content deleted: title and content deleted but test case created.
More info:
I cannot reproduce this bug when I edit the test case and change the status inside the description.
I have not been able to reproduce this bug with the online demo so I guess there's something wrong with my docker configuration or application configuration.
Any ideas on what could be wrong?
Thanks.

This is a bug which affects the latest available version. Already fixed here: https://github.com/kiwitcms/Kiwi/issues/1318
will be released in the next update.

Related

When clicking `Report bug` during Kiwi TCMS TestExecution no URL for editing is opened

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.

How to migrate an online angular script to local server?

Hi I'm trying to make an offline version of this page:
https://u-he.com/tools/microtuning/ the script is writtin with Angular JS how do I do that?
I saved the page control-s and copied the file to the local server I'm running.
And then I browsed the local ip. the page opened but I get repeated notes ng-repeat shows up as multiple boxes instead of 1 box that edits the same note but in different octaves.
How do I solve this problem please.
You can inspect the front-end code in your browser console. In Firefox it's in the section called "Debugger", in Chrome it's called "Sources". If you use Safari, you need to enable Developer mode first.
Once you have the appropriate view, just click on u-he.com -> tools/microtuning/ -> index
Hopefully it goes without saying that you shouldn't use large swaths of another person's code without at least giving appropriate credit, or better yet getting the developer's permission, unless there is an explicit open-source license.

Oracle ADF - Redirect link is not working

I am developing a simple application using ADF comes with basic CRUD operations (create, read, update, delete). In this case, as you can see, I have dragged a link to the 1st column which is highlighted in yellow.
So whenever I deploy it and click that, it is supposed to redirect me to the Edit page where client will allow to make commit:
I did make sure the Action of link is associated with the Edit page (as highlighted in yellow above). However, the link wouldn't redirect me anywhere, no response.This is the unbounded task flow:
Okay so I have found out the solution. Due to the default setting, the application will be deployed on IE and this message will prompt out. As you can see, the message is mentioning about browser's compatibility. My IE is version 11.6, I'm not sure what's the issue here since my IE is kinda latest version but this message still pops out and affects the redirect link from working. However, simply copy the application URL to Google Chrome and run should fix this issue. Hope this helps in future.
If the two pages in the Unbounded Task Flow, then Add WildCard Control Flow Rule
and connect the two pages with the WildCard.
Or you can use the Popup instead of opening a new page for edit

Umbraco - Menu always loads to route #/content after any menu click

I have just updated my site to latest version I have been notified about.
I have following issue:
Clicking on any link in menu in admin site (/umbraco)
The workaround I have found is
click on the link
click on profile
click edit
confirm that you want to leave the page
then the page reloads to correct page
or
I can reload manually by typing lets say
/#settings and the the angular routing does work
Now ever it is annoying and I cannot give it to anyone else to use like this.
Ok,
After few days investigation, I have copied all resources from my local pc to the server and to my surprise It works now.
This leads me to the following conclusion:
My project from which I have deployed my versions did not contain all the required files even if all the scripts successfully completed.
If you have same issue, copy all folder to the deployment location and this should do the trick.

Wordpress Error: Database Update Required

I'm currently working with a client right now that clicked to update a plugin on WordPress. He's unaware of what plugin it was that he updated because he's clicked update in the past for other plugins and they just updated, so he paid little attention to what it was he clicked.
His site is still up, but when I try to get into the back end using /wp-admin I'm hit with a message that states:
Database Update Required
WordPress has been updated! Before we send you on your way, we have to update your database to the newest version.
The update process may take a little while, so please be patient.
Update Wordpress Database
When I click on the button that says "Update WordPress Database" it does nothing. The browser spins and then shows me a blank white page with Wordpress at the top. I'm at a loss because I can't even login, it doesn't give me the option.
Any thoughts on what is happening? Thanks a bunch in advance for the assistance.
This is due to a missmatch between the databases versions you said you are using in the settings.
Please follow this steps:
Go to /wp-include/ folder and open the version.php.
Find the value for $wp_db_version, and write it down.
Now, open your database, check in the table called wp_options
Find the db_version value:
SELECT option_value FROM yourdatabase.wp_options WHERE option_name = 'db_version';
Those two values must be the same. Change it in the version.php file, not the database.
Source: http://wpquestions.com/question/showChrono/id/4151
Restarting php-fpm service helped me, it clears cache on restart
sudo service php5-fpm restart
Hope that helps some folks out there.
Try clearing your browser cache
The option db_upgraded isn’t getting set by the upgrade process.
Try this: go to /wp-admin/options.php. Fill the field db_upgraded with a 0 (zero). Hit Save Changes.
This is due to a missmatch between the databases versions you said you are using in the settings.
Please follow this steps:
Go to /wp-include/ folder and open the version.php.
Find the value for $wp_db_version, and write it down.
Open your database, check in the table called wp_options
Find the db_version value:
SELECT option_value FROM yourdatabase.wp_options WHERE option_name = 'db_version';
Those two values must be the same. Change it in the version.php file, not the database.

Resources