How do I convert from MiaCMS to Joomla? They both have a common ancestry in Mambo CMS (RIP). Now that MiaCMS is going the same way I need to move to something else and Joomla seems to be the best choice. There should be enough commonality to port over. And MiaCMS has a porting instructions from Mambo that could possibly be used to create a conversion script. I want to go directly to Joomla 1.5 if that is possible, although porting to Joomla 1.x and then upgrading would be an option. I tried to install Migrator (as described in the Joomla 1.0 to 1.5 migration guide) in MiaCMS but that didn't seem to work.
What I ended up doing was simply exporting the three tables mia_sections, mia_categories and mia_content as sql from my MiaCMS database. Then I replaced all references to mia_ with jos_. Then I could simply do a database import of the three sql-backup files into a pristine Joomla 1.5 installation. And Voila! all essential data converted.
Of course I had to re-populate and structure the website layout with appropriate modules but that was a fairly simple job compared to copying all the content by hand.
Template conversion turned out to be a hassle so I just started afresh from a properly designed Joomla 1.5 template and tweaked it to my liking.
Related
I am working on a Question Bank solution with over 5 hundred thousand questions in it's SQL Server database. The application runs on .Net MVC Framework. It uses TinyMCE as it's editor with Wiris MathType plugin.
The task at hand is to replace Wiris with a free solution keeping editing and rendering of the current questions in the DB with mathematical formulae intact.
What would be the best approach to problem?
All the solutions I have come up with either revolve around converting the existing data into latex style code and use an opensource latex plugin (which seems to be hugely cumbersome) or or develop custom plugin (which seems to be a project in itself).
I was wondering that since Wiris claims to use standard MathML, if there's a quicker solution.
Any thoughts and suggestions, please?
I am new to sakai, i want to add my own tool in sakai source code like announcement,syllabus...etc That tool having some my own functionality for this what i have to do, how can i develop my own tool in sakai.
Thanks.
Use one of the archetypes to get you started, then customise it. When you are comfortable you can change the UI layer to be whatever you like.
https://confluence.sakaiproject.org/display/BOOT/Developer+Tools
If you are looking for a solid "base" tool shell to begin with tool development my recommendation would be to start here: "Sakai Wicket Maven Archetype". There are a few other very good archetypes available but are often outdated and may cause you some problems based on my experience. This has been the one I've had the most success with.
This uses Wicket but does not mean you have to use Wicket to develop further with it. Make sure to pull the 1.2 version as last check the binaries for the others were not available yet so replace -DarchetypeVersion=1.4.1 with -DarchetypeVersion=1.2 It will compile and deploy successfully as a tool "as-is" that you can modify as needed. It also allows you to code in Java to directly access the sakai API and pull from its database or even add your own tables. I've successfully used it with NetBeans 8.0.1 and MySQL 5.6 under Windows 7 with Maven 3.2.3 and Sakai 10.1.
The code is well-documented and is no-frills but with enough varied functional use examples to allow you to do "almost" anything you want. The wicket manual is 600+ pages but in my experience you should be able to accomplish a lot just by looking at the code in the archetype.
I wish to create a document repository for my company. Reason is because my company have many documents and they did not have a version tracking in place. This means everyone is using different version all the time.
Plone is something new to me and i got to know from a good friend of mine. And too bad he is not around anymore to answer my question. I believed in him and i wish to materialize his idea, to use Plone as a document repository for my company.
I have install Plone and manage to view the default Plone page, add all company's username and change the logo to my company's logo. And now the biggest question is, how to setup the document repository? What i have in mind was to create a "page" for the user to add files, download files, search for files and read its description.
Any lead for me to go about?
Reusable,
Same problem here. We started to use Plone as our main DMS 4 weeks ago (inserting existing docs at present).
For working copies, we use iterate (insert plone.app.iterate under eggs in your buildout.cfg).
For versioning, Products.CMFEditions. I believe this worked out of the box.
For creating new workflow, look into plone.app.workflowmanager and read the docs.
In a previous question we asked, we were still looking at Dexterity which has alot going for it but eventually we decided on adapting an existing content type based on Archetypes.
As for inserting files, as long as the description is ok, they will be found through the in-built search functionality, but you might consider using Iterate mentioned above to make sure that nobody is using the same file twice.
As your new, as I am, the docs seem hard at first but are actually quite good.
And this book is still giving me the foundation we need to keep adding functionality.
Good luck
I think, you should get pretty far with vanilla Plone installation, without developing your own extensions or other customization add-on-products. Therefore, I'd recommend you to start with Plone 4 User Manual to find out everything you could do out-of-the box.
As #Speediro mentioned, versioning support comes built-in for the main content types (and you don't actually see CMFEditions mentioned anywhere), but it's not activated for file uploads. Although, as briefly mentioned in the manual: Content items can be configured to have versioning enabled/disabled through the Site Setup → Plone Configuration panel under "Types".
Working Copy Support (plone.app.iterate) should also be there already waiting for activation on Site Setup's add-ons-panel.
Yet, before the Plone Collective (=community) Developer Docs or Professional Plone 4 Development, I'd recommend Practical Plone 3. It has a bit outdated graphics (because it was made for Plone 3), but it's great next step after the user manual. E.g. how to define content rules to send e-mails notifications for content updates (still through the browser without coding). Or how to create custom forms using Products.PloneFormGen.
When you really need to write your own code, it'd be time for Professional Plone 4 and the Collective Docs.
If you can't have a developer to manage your stuff, I would recommand to stay on official Plone, no custom code and use only widly used addons.
I mean:
stay on the default theme (sunburst)
use the default plone content types
only customize the logo
activate plone.app.iterate in the addon controlpanel
do not play with workflow because they need to know what you are doing. by default a file has the visibility of it's folder. It mean if you can see the folder you will be able to see all files inside. You can just activate default worklfow for files under the ZMI.
Use collective.quickupload addon
Your database will going really fast to a huge size because Plone is doing indexing and indexing means lot's of spaces. So you will have to handle this as system adminstrator;
I have an OpenERP 5.0 installation with a few custom modules, that I wish to upgrade to OpenERP 6.0.
I have some experience with this kind of sofware and I have inspected OpenERP. Sadly, I don't have actual experience with OpenERP, and I like to ask for some help in order to avoid mistakes. When researching this, I found there are several strategies (ETL processes, data-upgrade modules)... I assume I'll need to review all custom modules.
What are the guidelines or best practice in order to upgrade an OpenERP 5.0 installation to 6.0?
We're still planning our migration from 5.0 to 6.0, so I don't have any personal experience with the process. We are planning to tackle the work ourselves, but we've done a lot of custom development, so we're pretty comfortable with the OpenERP code. If I were inheriting the system from someone else as it sounds like you are, I would be very tempted by the support contract that includes doing migrations for you.
In addition to the paid service, there also appears to be an open-source tool available for running data migrations. It is also discussed in several forum posts. (There really are a lot.)
Our tentative plans are:
Try out the migration tool for a demo database from plain 5.0 to plain 6.1.
Migrate the code for our custom modules to 6.1, following the Pragtech guidelines.
Extend the migration tool's configuration to cover our custom modules and any others that weren't included with the tool.
Run the migration on our full database into a sandbox and test the heck out of it.
Launch and celebrate!
Update:
We've started our migration process, and we're using OpenUpgrade instead of the Domsense tool. We never really looked at the Domsense tool, so I can't say which is better. I'm very happy with OpenUpgrade so far.
In general, I've found version 6.1 much easier to customize than 5.0 was. So far, I haven't had to change any core modules. For example, most places where a core module inserts a record, it calls a helper method to prepare the data. If you add a new column that you want to be populated, you can just override that helper method. For example, we added a grouping field to several tables and then wanted to copy it from sales order line to stock move. We overrode the sale module's version of sale_order._prepare_order_line_move() with our own version.
I posted a separate question about customizing reports.
The down side is that every customized feature we try to migrate requires some change. So far there has always been a change in the core module that somehow breaks our customization. Either a field name changed, or the screen layout changed, or the whole model name changed. You can usually figure out how to fix it, but everything takes time.
The best approach is to contract an OpenERP Enterprise. Migrating is quite complex and OpenERP can do the job for you. It's a fixed price for unlimited bugfixes and migrations: http://www.openerp.com/catalog/146
I have been look around for Free/Open Source ASP.NET CMS / Portal systems for a while now, and have seived it down to two different ones.
Umbraco - http://umbraco.org
mojoPortal - http://www.mojoportal.com
Both look excellent and have different appealing features, but I am looking for people who have used both and which one you went with and why??
I actually went for Umbraco in the end and would never look back, its incredibly easy to install and use
To install you can use the web platform installer to install it and the AMAZING amount of free projects you can EASILY install with a couple of clicks make it by far the best CMS out there
http://our.umbraco.org/projects
If you are unsure where to start have a read of this
http://www.blogfodder.co.uk/post/A-Complete-Newbies-Guide-To-Umbraco-CMS.aspx
I tried Umbraco and it is not for the timid. I feel I'm a fairly technical person, Sr. Web Developer... and after several hours I gave up.
MojoPortal just works.
It has its flaws, but the simple fact that it just works means it wins.
I used Kentico, DNN, Sitecore, Joomla, CMS Made Simple (Yes admittedly not mojoPortal). Umbraco is by far the most powerful if you are after a highly customised and highly specified solution. Linq2Umbraco just seals the deal.
However, if you are after idiot proof CMS with everything built in, and your biggest concern is to look for check boxes to enable forum/blogs/whatever other joke modules/bells and whistles/etc. Umbraco isn't for you. IMO Kentico/DNN are the ones.
Edit - And 3 years later, I've used SharePoint, epiServer, SiteFinity as well.
Umbraco still wins hands down.
mojoPortal seems easier to use to me and it works even with javascript disabled like using noscript browser plugin. Seems more care of accessibility has been taken using progressive enhancement javascript techniques whereas you can't manage your site at all with javascript disabled using Umbraco.
I haven't tried mojoPortal, but I love Umbraco.
Things I like:
Clean code
Uses XSLT, python, or .NET to extend
Awesome community support
Tutorial videos for easy learning
Admin area is extensible
Good plug-in projects
But really its because I can use it for both small and large projects easily.