When i am creating issue in Testlink asking version and not taking any data in version field. Please help me what is version exactly has to be.enter image description here
The Version field is empty because you have not specified any versions for your project in JIRA. In my case it was Fix version in JIRA. Currently the rest API is getting an empty list of versions. You can try
curl -X GET http://xxx.yourjiraserver.com/rest/api/2/project/MX/versions
-H 'authorization: Basic usidjdfkbusjiddosksjsjasidDkw'
This will give you an empty list.
Once you set FixVersion for your project in JIRA, this API will return the list of available versions for your project and the Version field will be populated with those versions.
PS: use your own authorization headers. You can use Postman for this purpose.
Related
I continue to get this error message on my wordpress front page:
Warning: Cookie paths cannot contain any of the following ',; \t\r\n\013\014' in /var/www/aveugle-shop.com/public_html/wp-content/plugins/woocommerce/includes/wc-core-functions.php on line 1035
I can't figure out why this message is showing?
My hosting said that it was because they updated their php database (or something), and all i needed to do, was to run back their old one, by inserting a snippet into .htaccess file.
This worked for a day or two, and now it's showing again.
Do anyone know what the actual issue is, and how to fix it?
My woocommerce status also says this on a bunch of plugins, and i don't know if that's the fault:
Installed version not tested with active version of WooCommerce 4.4.0
I dont know if this is the correct solution but I got the same error just now.
It happened to me when I upgraded PHP from 7.2=>7.4.
It seems to originate somewhere from the database because I solved it by just importing the database again from my testserver, same database, same codebase but all of a sudden, it started to work after reimporting db... A cache issue maybe?
How can I deactivate the fe_typo_user cookie in TYPO3 7.6. I don't use fe_login or other data stored in sessions on this website, but the cookie is set. The website was updated from an earlier TYPO3 version. In this issue another user had the same problem with an updated version - as solution he obviously used a fresh installation of TYPO3.
Isn't there another way to deactivate this cookie if not used? In earlier versions it worked with
["FE"]["dontSetCookie"] = 1
but in 7.6. obviously not anymore.
Edit:
The cookie is set new. I deleted it in chrome developer tools. You could check this webiste. I use powermail for contact forms, but as far as I know it doesn't set cookies. For tracking Piwik/Matomo is used, but it has it's own cookies "outside" of TYPO3. Conditions aren't used.
Which version of powermail are you using?
Since v6.0 the session-spam-check is disabled by default.
From release notes:
Task: Disable session-spam-check by default (to prevent generating a cookie)
Are you sure the cookie is set new?
You need to identify where you have user-dependent configuration which might set the cookie.
Do you have forms or interactive elements in the site?
Do you have conditions in your configuration?
Do you use tracking tools?
I have developed a collection in postman having a bunch of API Endpoints. I can add team member to my Postman workspace and also can share the Documentation link publicly online.
What I was finding to have a download link to download the documentation as a folder so that I could add them into my project.
Is there anything I failed to find in postman?
You can export the collection as a json as shown in the other answer and then run a tool to convert it into an HTML document that you can host wherever you want.
I created a simple python executable to do just that -
https://github.com/karthiks3000/postman-doc-gen
Hi #Siddiqui currently this feature is not available, I do it by going to my collection documentation and getting it to print when the print prompt is shown I save the document as PDF before finalizing the print options. Once I get it in PDF I have all sorts options to do as I want. This is the closest I have been to downloading my collection documentation.
I have redacted information for privacy.
Hope this helps or leave a comment if I can be of any further assistance.
Postman generated API documentation is meant to be shared and consumed via workspace and URL to help ensure it is kept up to date and does not go stagnant. Because documentation will most likely be regularly updated with examples, new endpoints, and other elements anything downloaded will quickly be out of date. I know that a PDF generated version has been discussed as part of future releases, but keeping API documentation up to date is the priority.
A simple solution to this is to print the page to PDF from the web browser. It's not perfect but it is usable.
https://learning.postman.com/docs/getting-started/importing-and-exporting-data/
to export the doc to json
and then run the script by #karthiks3000 (https://github.com/karthiks3000/postman-doc-gen)
I have used TYPO3 8 Latest version with repository extension sr_feuser_registration(5.0.0) and my systems using php version 7.1.99.
Edit User profile is not working. when i click on update profile button it's just refresh the page not update profile. Also i debug the code and i get always isSubmit value false. but when i enable editPreview then update profile working fine.
Thanks!
There are several related bugs posted on forge.typo3.org.
Alternatively you can try femanager.
Im using WSO2 Governance Registry 5.2.0.
When I create a new artifact type, it containt a lot of new fields (You create and define this XML in the CARBON ADMIN CONSOLE). So in the PUBLISHER you can see the new fields, create and consult a new item of the artifact.
But the problem is in the STORE, I cannot see the this new fields. So in order to do this, I made the custom fields available by modifying
GREG_HOME>/repository/deployment/server/jaggeryapps/store/extensions/app/greg-store-defaults/themes/store/partials/asset-attributes.hbs file. Thanks to Malintha's Blog,
This is perhaps an answer, but it will get much worse if for each artifact I have to edit the file to add the fields, editing this file will get a lot worse over the time...
So my question is: Is there a way to create a custom theme (*.hbs, etc) for each new artifact I create?
THANKS!
As far as I understand your in the development phase of the project that you have to create registry extensions(RXTs) and showing up the data in G-Reg Store. As far as I know there is no easy dynamic way that you can do this, either you have to extend the default hbs files. Like you have done using Malintha's blog. This is okay if there is a minor change to be done, However this is not the recommended way because if there is a migration to do such as moving to all new WSO2 G-Reg 5.3.0 you might face lot of trouble if you updated the out of the box files in G-Reg 5.2.0, Therefore I suggest you to write asset extensions(GREG_HOME/repository/deployment/server/jaggeryapps/store/extensions/assets) for each and every rxt that you are going to introduce. There is plenty of blog posts that can help you.
Please find the below list of blog posts(I will update the list if I found any).
Adding a New Asset Type
How to view the json payload sent to the Store UI in GREG 5.1.0
How to extend an asset's store view in WSO2 GREG 5.1.0
WSO2GREG-5.2.0- WRITING EXTENSION TO REPLICATE MORE ARTIFACT
METADATA IN STORE
Overriding default "look and feel" of GREG - 5.3.0
Note:
There is no much difference between 5.1.0 and 5.2.0.(5.2.0 is more stable)
You can start(learn) creating a new extension by simply extending restservice.rxt and the relevant asset extension(GREG_HOME/repository/deployment/server/jaggeryapps/store/extensions/assets/restservice), I prefer you to use this blog post and start from there.
If there is a lot of development to be done I prefer you to seek help from WSO2 experts from they're official portal, if not you can always stick to stackoverflow.