How do I migrate a forum from phpBB 3.0.9 to nodeBB 1.14.2?
I've found some plugins but I'm pretty sure the version differences will cause major headaches :
importer wrong phpBB and nodeBB verions
migration exporter ?
exporter closest version match but not quite : pbpBB 3.1
post migration, convert to markdown
Also I'm not quite sure of the procedure?
Is it remote connect to the phpBB server stop the forum and install the exporter plugin then start the forum and pick up the entire forum as one database file, then stop new nodeBB forum install plugin then start the new forum and import the file?
it's unclear from what's given.
I also have some perhaps unusual requirements :
I'm not interested in migrating accounts, in fact I specifically do not want to migrate accounts. the migration exists only as comfort for those who want to be able to look up the old archived threads (btw I will mark them all as read-only after migration) but effectively we are starting from scratch with new accounts.
So I'm not interested in migrating the accounts and I'm wondering if that's an issue? do posts necessarily need to be created with an account or is creating posts made by an unattributed user name possible? (if nodeBB attributes posts from the old forum archive to a new forum joinee that's perfectly fine by me, not so if nodeBB refuses that a new joinee use that name under pretext that it's already under use. New users and content must take priority)
will nodeBB allow this or will it require a account named "archivebot" for example to be "responsible", the "author" of all these posts. I'd prefer if I could at least preserve the author names but if I can't that's an ok sacrifice.
Also will nodeBB allow the original dates for the posts? or will all of them be of the date of the migration?
TLDR: I don't know how to migrate from phpBB 3.0.9 to nodeBB 1.14.2 specifically there doesn't seem to be an upgrade path for those specific version numbers.
Related
I recently upgraded an old store from 2.0.1.1 to 3.0.3.8 but to comply with PHP8 I need to upgrade again from 3.0.3.8 to 4.x. My question stems because I was able to successfully install the new 4.0.1.1 storefront, but I am no longer able to access my admin panel. Attempting to login to my admin will always give me the error that the account does not exist.
I have double checked the config.php files in both my root & admin folders and the database information stored there is correct. Also, I checked my actual database to make sure the user accounts weren't deleted in the upgrade and they were not.
I don't see a lot of documentation about the upgrade process to a 4.x OpenCart storefront so I am coming here in hopes someone has been brave enough to attempt this upgrade that may be able to point me in the right direction. Some tips and tricks would be greatly welcomes because I imagine this is just the first of many moles I am going to need to whack.
Let me know if any code would be needed/handy, but keep in mind this install is basically all stock barebones at this point because I haven't even tried to activate my custom theme yet (mostly because I can't access the admin to activate it).
Solved this by upgrading to the OpenCart 3.x.x_Maintenace branch, instead of OpenCart 4.x.x version, as it is also PHP8 compliant and much more stable.
For anyone with similar issues, they can refer this link.
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.
I have a Django site and a local install of Alfresco (community edition). One of my model contains a file reference which maps to a document in Alfresco. The view should have a field that spawns a file browser that can access the repository structure within Alfresco so that the user can pick whichever file they want at whichever version.
I looked at the CMSIlib module and it seems to be providing all the interaction I need for the back end code. Although downloading a document seems clunky.
There are lots of Django file browsers but none seem to interface with CMSIlib.
Do I have to code my own or have I missed something?
The version is Alfresco Community v5.0.0 (d r99759-b2) schema 8022 Spring Surf and Spring WebScripts - v5.0.0.
To be honest, I am not a python guy ! But I heard over the official #alfresco IRC channel that cmislib is not so much of an active project, and questions about it only bump once in a while .... The RESTful api however may be considered as a good alternative in your use case:
To access alfresco content using the RESTful api, you should be querying this webscript: /alfresco/d/<d|a>/<workspace>/<store>/<nodeId>/<filename>
where :
d and a refer to direct / attached mode
<workspace>, <store> and <nodeId> reference your content nodeRef
<filename> a file name of your choice
So you should be making a GET Request an a URL that looks something like this http://<host>:<port>/alfresco/d/d/workspace/SpacesStore/8444ad61-4734-40e3-b2d4-b8b1c81347fd/myFile.ext
Note : Depending on the permission set on your node, you might need to attach an alf_ticket to the URL for an authenticated alfresco user. Please check this for further insights.
UPDATE 1:
If you have a problem identifying your file nodeRef, then you can setup a repo webscript implementing your custom logic (browsing some folder / searching for a document by name or metadata ....)
If your are not familiar with webscript development check Jeff Pott's tutorial on the subject
UPDATE 2:
To get started with your webscript development check out Alfresco docs/wiki!
Check this wiki page to learn how to retrieve children for a given node !
Or check this wiki page to learn how to develop webscripts implementing your custom business logic.
If you do not have anything against the YUI javascript library (that is no longer actively maintained), you can integrate the object-finder already available in Alfresco Share. The library is in
share/components/object-finder/object-finder.js
You will need to modify it a bit given that you are not inside Share.
To be totally honest, I do not know if it is feasible because it has other dependencies but being a browser site library, in theory can be integrated everywhere.
I met the django-uploadify (multiple file uploading) application, but the only template-use is described in wiki of the project. I need to integrate it with django admin. Any ideas?
#rebus and #Mordi have good suggestions; one of those is probably your best bet. Still...
The current implementation of file uploads in web browsers is single file only. That's a limitation of the HTML standards and the browsers themselves. When you see multiple file upload capability (all at once / select multiple) in some web app, something like Flash or Java is in play. You could potentially use a Flash or Java applet (check out Uploadify - about the easiest to work with you'll find), if you wanted, but you'd have to do some work tying it into Django: namely mapping the output of the applet to the input the Django Admin expects on POST.
Personally I found this package to be painful when I attempted to do this locally. It is 7 years old and not maintained. django-filer is a more modern implementation that has this exact functionality built into the admin panel, it was quick to set up and it seems to be maintained a lot better. And the UI is excellent!
If your really set on using uploadify my attempt was quite painful. When I went to the website to download the uploadify jQuery plugin it was a paid download. After looking a bit I found a fork, and was able to get it going locally, but because the python package is old it required a lot of changes from python 2.7..
To integrate this with your project in the admin will definitely require you to write your own custom admin template. In your admin.py you would have to override the default template and methods, this faq has some insights. In your new template you would include the uploadify jquery script and put the upload file field inside the form where your model fields would be. When you upload files the signal sender in the package will fire, and you would just have to intercept the signal and handle it with your intended logic
Very easy to implement multiple image upload with this project:
https://github.com/tstone/django-uploadify
We've got a company wiki running Mediawiki on our intranet that has been in use for a while. We just recently installed Redmine and are in the process of getting it configured just the way we like it.
I was wondering if there's any way to use our already existing wiki instead of the built-in one that comes with Redmine. We've got alot of articles & documentation written by non-developers and don't want to lose and/or re-import into another wiki (ie redmine's). The Wiki portion of redmine will not allow me to enter the url for the external wiki as it includes various illegal characters (mainly : and /)
Edit: As a temporary work around, I've just used each project main page on the "external" Wiki as the Projects "Home Page" in Red Mine, so far this is the best I've been able to figure out. You don't get Wiki access from the various issues & what not, but the link to our other Wiki does show under the Overview for each project now.
Btw, both of these are installed on the same physical box, a Windows 2003 Server, where Mediawiki was installed using a WAMP package, and Redmine was installed pretty much manually instead of using a stack like Bitnami.
Did you see this MediaWiki integration patch for Redmine? http://www.redmine.org/attachments/572/redmine-mediawiki.patch and its reference page http://www.redmine.org/issues/617 I have not used it so im not sure if it meets your needs but it might be worth a shot. (Be sure to backup first)
The reference page says this about the patch:
Here's a patch for 0.7 that will add a
MediaWiki tab to your project settings
and integrate it into the issues
pages. You will also need to add:
is_mediawiki tinyint(1) NOT NULL
default '0', mediawikiurl
varchar(255) NOT NULL default '',
mediawikinamespace varchar(255) NOT
NULL default ''
To the projects table for this to
work.
I know you didn't want to import but just in case someone else did here is a rake file for importing MediaWiki pages into Redmine http://www.redmine.org/issues/1224
We looked into this as an option since there are so many tools that work with mediawiki however we decided not to pursue the option since we already had so many issues and wiki pages in redmine. As far as I can tell, this patch replaces the existing redmine wiki input boxes with mediawiki boxes. This is done not only in the wiki section but also for issues and documents. We were afraid of:
Losing all of our existing wiki pages, and issue descriptions.
The whole thing breaking as Redmine updates are posted and installed.
We have found that the newest Wiki Extensions plug in http://www.r-labs.org/projects/r-labs/wiki/Wiki_Extensions_en has given us most of the features we wanted for the wiki part. It has comments, voting, tags, and many other things. It works well with the latest version of Redmine.
We still are trying to find a good way to import into the wiki all of our existing documentation from word.