(1)
Your rating: Now say why...
- Download Now
8.38 MB -
Visit Developer's Site
The Midgard Project
Midgard CMS is an open-source Content Management System built on top of the Linux, Apache, MySQL and PHP (LAMP) platform. It provides a reliable, powerful and internationalized set of tools for building web sites and networked applications.
Midgard utilizes PHP as the web scripting language and provides integration interfaces on Java and C layers. Midgard's unique architecture enables it to provide services like single sign-on and replication. With these capabilities and the integrated full-text search system, Midgard is an excellent match for information-rich web sites and
Midgard utilizes PHP as the web scripting language and provides integration interfaces on Java and C layers. Midgard's unique architecture enables it to provide services like single sign-on and replication. With these capabilities and the integrated full-text search system, Midgard is an excellent match for information-rich web sites and
What's New
Version 1.8.2:
Main changes from 8.09.8:
- Rewritten Multilang queries (#1776)
- Fixed crashes (#1547, #1684)
- Fixed major MidCOM admin and style issues (#1779, #1788)
- Midgard internal features are now optional for better performance tunning (#1851)
- Many bugfixes and feature enhancements
- Usability of the on-site Midgard toolbar has been enhanced (#877, #1624)
- Performance when using the MidCOM content cache has been improved (#1599, #1531, #1048, #1577 and #1584)
- bundled jQuery javascript library has been upgraded to version 1.4.2 (#1596) and jQuery UI to 1.7.2 (#696)
- PHP 5.3 compatibility on both php5-midgard (#1433) and MidCOM levels
- Asgard now shows contextual helpers when creating Midgard templates (#1595)
- Midgard is able to act as both OpenID provider (#1664) and consumer (#1709)
- Fixed SQL errors in complex Query Builder queries (#1625)
- Fixed midgard_connection environment settings in Apache environment (#1689)
- midcom.helper.datamanager was deprecated in favor of datamanager2 (#930) and will be removed in 8.09.9 (#1715)
- Updated OpenPSA packages (#1655)
- Fixed crashes in content replication
- Fixed deleting Multilang objects (#1522)
- Fixed installer crashes (#1421)
- Admin and user UI fixes (#1141, #1415, #1447)
- Improved page symlinks feature (#1548)
- This release requires database update to be done by datagard.
- Fixed multilang content replication (#1392)
- Improved performance of some multilang SQL queries
- New datagard options to install Midgard or PEAR packages (#1204, #1352)
- New datagard option to install full OpenPSA application instead of a Midgard CMS site (#1204)
- Midgard now ships with SElinux setup files
- Fixed SG0 authentication issue (#1390)
- Several optimizations when querying multilingual objects
- There is a new optional object cache (#1256)
- There is a new view for displaying a deleted object in Asgard
- Authentication routines fixes (#485, #765)
- Fixed major memory corruption in php5-midgard (#1054, #1058)
- Midgard installer improvements.
- Midgard installer doesn't depend on pearified.com channel (#747)
- Memory corruption in midgard-php extension has been fixed (#804)
- Query Builder and Collector constructors has been improved (#556)
- Several crashes has been fixed (#712, #734, #801, #870)
- Internal PHP classes can be introspected by PHP Reflection (#479)
- midgard_cron has been improved (#813, #816)
- URL name handling and generation has been rewritten (#809)
- TinyMCE WYSIWYG editor has been upgraded to version 3.2.2
- Issues with handling multilingual content have been fixed (#870, #825, #935, #865, #910)
- Code editor in Asgard has been changed from CodePress to EditArea
- Configuration editor in Asgard now always creates valid configuration snippets (#771)
- MidCOM now uses only the modern Midgard2 API (#611)
- PAM authentication has been fixed (#750)
- Midgard now ships with SELinux policy files (#538)
- MidCOM DBA has been rewritten to follow decorator pattern instead of inheritance (#456 and #599)
- There is a new online help and documentation viewer
- Safari user experience has been greatly improved (#583, #585)
- Basic authentication on Midgard level has been fixed (#485)
- MidCOM cron is now automatically set up for new virtual hosts (#378)
- All legacy metadata fields have been removed in favor of midgard_metadata object (#387, #464, #476 and #477)
- Replication has been changed to work using the new API and decorators (#627, #607, #534, #501, 513, #564
- File attachments now have MultiLang emulation (#420)
- In-page Ajax editing can now be disabled and enabled globally (#526)
- Midgard's tree management has been improved in many ways (#447, #482, #483, #600, #602, #625)
- HTTP errors can be mapped to notifications or special logging (#305)
- The Midgard PHP extension is now approximately 50% faster
- MySQL errors when upgrading old databases have been fixed (#355)
- SQL queries generated by MidCOM's DBA layer have been optimized (#412)
- Midgard now sets up a standalone Asgard administrative interface for
- all new site setups (#36 and #329)
- MidCOM has a new handler for catching PHP Exceptions (#352)
- MidCOM DBA is bypassed for configuration and element loading (#414 and #415)
- Midgard Collector is now able to query metadata properties (#417)
- MultiLang support has been improved with index articles and
- attachments (#288 and #420)
- Debian and Ubuntu packages now automatically install memcached and
- SOLR (#380 and #381)
- Datagard upgrade from 1.8 now installs same MidCOM packages to
- Ragnaroek (#363)
- Swedish translations are now included
- Midgard and MidCOM now follow an unified release schedule and roadmap
- There is a new command-line database and website setup utility
- There is a new Site Wizard web interface for website creation
- PHP4 support has been removed in favor of PHP5
- GObject attributes of Midgard objects are directly mapped to PHP objects for performance reasons
- Repligard package has been removed and replaced by new built in replication API
- The MidCOM framework uses autoloading to reduce memory usage and processing time
- Prototype Javascript framework has been removed in favor of jQuery
- New Midgard logo and graphical guidelines have been deployed across the system
- Packages are built for several Linux distributions using the openSuse Build Service
- Classic Midgard API has been deprecated in favor of MgdSchema and Query Builder, but is available via --with-legacy-api configuration switch in midgard-php5
- midgard-config command-line tool replaced with Midgard configuration supported by pkg-config
Version 1.8.2:
Main changes from 8.09.8:
- Rewritten Multilang queries (#1776)
- Fixed crashes (#1547, #1684)
- Fixed major MidCOM admin and style issues (#1779, #1788)
- Midgard internal features are now optional for better performance tunning (#1851)
- Many bugfixes and feature enhancements
Requirements
PPC, Mac OS X 10.4 or later
PPC, Mac OS X 10.4 or later
Be the first to recommend a similar software title.
Midgard CMS User Discussion (Write a Review)
Overall:
(1)
(1)
| Downloads:5,052 |
| Version Downloads:1,786 |
| Type:Development : Networks |
| License:Free |
| Date:30 Jan 2007 |
| Platform:PPC |
| Price:Free |
Overall (Version 1.x):  |
| Features: |
| Ease of Use: |
| Value: |
| Stability: |
-
-
-
Midgard CMS is an open-source Content Management System built on top of the Linux, Apache, MySQL and PHP (LAMP) platform. It provides a reliable, powerful and internationalized set of tools for building web sites and networked applications.
Midgard utilizes PHP as the web scripting language and provides integration interfaces on Java and C layers. Midgard's unique architecture enables it to provide services like single sign-on and replication. With these capabilities and the integrated full-text search system, Midgard is an excellent match for information-rich web sites and intranets.
Midgard is available for Mac OS X (Tiger) as an installer package that contains both Fink and Midgard CMS.
Midgard utilizes PHP as the web scripting language and provides integration interfaces on Java and C layers. Midgard's unique architecture enables it to provide services like single sign-on and replication. With these capabilities and the integrated full-text search system, Midgard is an excellent match for information-rich web sites and intranets.
Midgard is available for Mac OS X (Tiger) as an installer package that contains both Fink and Midgard CMS.
Copyright © 2012 MacUpdate LLC
- -
+2
The systems mentioned earlier, Mambo and Joomla, are both available.
Anonymous reviewed on 21 Aug 2005
Anonymous reviewed on 20 Aug 2005
The reason Fink and midgard were packaged together was to have a simple, one step install process.
A more complex way to get Midgard working on OS X is to install from sources. That takes time, but is well worth it. Instructions on how to compile from source on OS X are @ the URL below:
http://www.privaterra.org/blog-rg/midgard-mac-os-x-10-4-2-installation.html
As for Midgard as a framework - one needs to understand that it is that, a framework , and a very powerfull one at that.
The installation is for the advanced user. if you are such a user - then, by all means try instead to build from source.
Anonymous reviewed on 20 Aug 2005
ARRRGGHHH! It is a pain. I have much experience with CMS systems and this smelt of elderberries (that, by the way, is a bad thing).
The installer will install all the Midgard stuff AND Fink. All told you will get just OVER 2GB stuffed into your hard drive. Hello?! That is waaaaay to much stuff for one install. How about a warning next time, sheesh.
The directions say you should launch the package installer, do what it says and then visit http://127.0.0.1/midgard to enjoy your new CMS. Not true. Since everything was installed in the newly created /sw directory it is invisible to you webserver. You will need to create a virtual directory in Apache to get this pointed to the correct place. You also need to set up a MySQL database.
The gist of it is, download their package, install it and... nothing. It is more complicated than they portray.
Not closely enough, obviously. Though I use Darwin Ports and don't want Fink cluttering up my hard drive.
>The package installs both Fink and Midgard CMS.
I wanted Midgard. Not Fink.
>Once you've run the installer only thing you need to do is start Apache and MySQL from /sw, and log into Midgard using your browser.
OS X already has Apache installed. Why do I need to install another instance and run it from this non-standard location?
I'd suggest you eliminate Fink from your package, tell folks where they can get a copy of MySQL, and let them use the version of the Apache server that is already installed on their machine.
Actually, yes. It is built from source in the sense they mean. When it provides a binary distribution, fink just provides a compiled-up milestone along the ‘build from source' route.
This shouldn't be using fink. It should have Apache and MySQL as prerequisites, then you can use your own solution, like WebEdition's distro.
CMSs are famously screwy, whether free or commercial. It makes me wonder why people don't use Wikis more frequently. (But setting up Mediawiki is another nightmare all its own.)
Anonymous reviewed on 20 Aug 2005
I would recommend potential users consider a number of additional systems when evaluating a CMS. Namely Mambo and Drupal. These are "plug and play" systems that don't require much customization to get up and running and are quite powerful.
If you are a designer at heart (as opposed to a programmer), you will like Textpattern. It seems complicated but is actually the easiest to customize the look of (just have decent XHTML and CSS skills).