We've been running a Mantis 1.1.8 install for some time. Recently, we had a need to export a project. As such, I upgraded to 1.2.5 following the instructions here: http://www.mantisbt.org/manual/manual.installation.upgrading.php
Now, I'm trying to export the project as XML from the View Issues page. I've got about 100 issues to export (for this test), and Export XML is returning a blank XML document. Exporting as a CSV is working fine. Any ideas why this is?
I've tried a number of different variants, with no success.
Assuming this is still an issue after all this time, note that I recently committed several improvements to the XML import/export plugin. I suggest you download a nightly build and check if the export works now.
Try installing XML support for PHP first.
Related
The dump comes from exporting a snapshot from AuraDB, as stated in Neo4j documentation.
im working with Neo4j Community 4.1.11 in Ubuntu, none of the other answers i found have been helpful...
Let me know what other piece of info you need to assess better the situation, thanks
when running the command...
You may need to upgrade your local version of Neo4j to something much more recent - an Aura database I just created couldn't be loaded into any version of Neo4j older than 4.4.1 (as at current date).
However, the specific version you need to use will change over time.
Guidance on the Aura support site indicates as much, and recommends using the latest possible local version of Neo4j as the target for the import (potentially to the point of needing to use pre-release versions), since Aura will typically be running bleeding-edge versions of the database store format.
An alternative might be to explore exporting to CSV or JSON and importing that way, since this output won't vary depending on Neo4j version of the source or target - you can do a stream-based export from Aura using apoc.export.csv.all or apoc.export.json.all which you could then load via script, though with large graphs this may not be practical.
I have built a graph in Neo4j 2.2.0. I have validated it by using Cypher interface querying etc. Now I want to import it into Gephi 0.8.2. I am using neo4j plugin (not sure of its version. Its downloaded through the tool)
When I try importing my neo4j database it gives blank error popup, no information on it. I tried to import defaultdb which comes with neo4j, the exact same behavior. So I suppose its not to do with database but some configuration or version etc.
I also enabled debugging option in etc conf setting of Gephi.
-J-Dnetbeans.logger.console=true -J-ea
But this is not opening or printing anything. I also tries to find Gephi log file which I cannot. Could not find anything of google. Any idea what may be going on or how to debug/ see log file etc? Appreciate any help
You want to try the following in Gephi
1. Go to Tools - > Plugins - > Updates
2. Select all the plugins listed and click update
I found a way to get around this obstacle.
you can export your data from Neo4j to a CSV file, and then upload the file to Gephi.
hope it gets you what you need.
I am building on Hottowel spa template and my solution was working fine for Read, Save and Update. Delete was failing though with "Object reference not set to instance of object". At this point the Breeze.webapi verison was 1.2.0.0. After reading some articles, it was suggested to update the breeze to latest version.
I updated the breeze framework using nuget package manager and now, it fails while parsing the metadata - It says JSON string returned from the server have parsing errors. But when I look at the JSON using JSON formatters in chrome. It looks just fine. This is happening with Breeze.webapi version 1.2.8.0.
Now, if I switch just the breeze.webapi dll back to ver. 1.2.0.0. Metadata part works just fine again, however delete doesn’t.
Any help is appreciated
The likely cause is that the NuGet update did only part of the job and left your application with a mix of new and old Breeze parts. You could see that this happened by looking in the Package Console window but most folks don't look. Having been burned with every NuGet package upgrade I can think of, I now watch that console like a hawk.
I think you'll get out of trouble if you completely uninstall Breeze and re-install the latest. Look at that output window carefully. If it fails to remove something (as it might), there will be a warning to that effect. Please delete that lingering item manually before re-installing.
I'm talking to John about updating the HotTowel template so that upgrading the Breeze package feels less urgent.
Sorry for your pain.
With issues gathering on bitbucket, I'd like to have a way to gather and back them up in the event that I need an offline copy, or no longer use Bitbucket, or something else. The site doesn't offer this service. Is there an alternative mechanism I can use?
From now on you can Import/Export your Issues:
Goto: -> Administration -> Import/Export
Youtube-Video: Bitbucket Issue Export
You can get your issues via the Bitbucket API.
Here is an example URL to get the issues for one of my projects:
https://api.bitbucket.org/1.0/repositories/christianspecht/bitbucket-backup/issues/
However, this returns a list of the issues in JSON format.
I doubt that you can do anything useful with a list of issues in JSON, but I don't know if there's a better file format for issues.
I just asked exactly that here on StackOverflow, because I'm dealing with the same thing at the moment:
Is there a standard file format for exporting issues from an issue tracker?
Full disclosure I am the author of Issue2Markdown because I really needed it.
As mentioned previously you can export your issues from Bitbucket project by going to Settings->Issues->Import & Export and then downloading the resultant ZIP file.
Inside that ZIP file, you will find JSON file and attachments archive. You can import those into some other issue repository. Or if you are like me you may be working with a remote team that is reluctant to use an issue tracker and would like to be able to read a human-readable version of the issues.
That is where Issue2Markdown comes in. You can use that to render your issues as a single Markdown document. You can find pre-built binaries for Linux, Windows, and MacOS under releases.
I hope that helps the next person who could not find the solution.
There doesn't currently appear to be any way to export your issues :(
You could export issues from settings in the repository. Then download the and extract the zip file, that would give you a json that you just could parse any way you prefer
I wrote a small python script to convert issues json file to excel that you can find it here. Hope it gives you some ideas:
https://github.com/anath2/bitbucket-issues-to-excel
We've been using a free commandline utility called PDFTK which we make a system call to from a Ruby on Rails app to split PDFs into individual pages. However, it only supports PDF Version 1.4 and back.
Can anyone recommend another utility or gem/Rails plugin to similarly manipulate later version PDFs?
Thanks
pdftk is built on iText (dated 2002). It should be possible to tweak it so that it builds with the latest version of iText, or alternatively install java and call iText directly.
There is another compilation v2.01.
I have tried with v1.5 specs PDF file and it works.
Get it at: http://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/