Martin Gottlieb schrieb:
Well, I can go to /midgard, where I initially get "Site Initialization
missing". I click on Proceed to Initialization and that seems to go
just fine. Then I click
on "Back to Site Administration", which brings me to the "MidCOM CMS
Site Administration" screen. It is when I click on the "Content
Authoring and
Site Administration" link (/midgard/midcom-admin/ais/) that I see the
error in my log about midcom.admin.content.
But if you see AIS, you're most definitely on 2.4, this doesn't exist in
later versions. Have you tried outputting the value of the MIDCOM_ROOT
constant? It should point to the location of your pear install. You can
define it in the code-init page element:
if(!defined('MIDCOM_ROOT')) {
define('MIDCOM_ROOT','/usr/share/php/midcom/lib');
}
Maybe I am completely in the wrong place. /midgard was pretty much the
only entry in the host table (other than my sites). Though I just also
found that there
is a host for /midgard-sitewizard. When I try to access this page, I
get the following error:
PHP Fatal error: Class 'midcom_baseclasses_components_request_admin'
not found in
/usr/share/pear/midcom/lib/midgard/admin/sitewizard/admin.php on line 16
If I do end up needing to manually add the host records, how will I know
what root and style to use ? What are the names of the site and style
in midgard itself. I can
use Aegir to find them and grab the IDs.
But if I understood your post correctly, you have a running midcom
site under http://url, right? If you login (with
http://url/midcom-login-), do you see the toolbar?
/midcom-login gives me a 404.
There has to be a dash at the end, but I think the problem is simply
wrong version.
/midgard/midcom-login take me through the
same initialization stuff I mentioned above. No toolbar.
BTW: You mentioned that you upgraded from 2.4 originally. Did you run
the upgrade script (called migrate_26.php in the support folder)? I
remember it took me something like three weeks to figure all the
details out, so I'm kind of surprised (and jealous :-) to hear the
conversion went so smoothly for you (underlying theory: Is the site
maybe still running 2.4 without telling you for some reason? Do you
see the version number somewhere in the rendered output, like f.x. in
the meta tag generator in html head?).
I did not explicitly run midgard_26.php. Would that have been called
when I ran the update option in datagard ?
Yes, datagard doesn't really care about the installed midcom version.
there's an article here that mentions most of the things that need to be
done to get to 2.6:
http://www.midgard-project.org/documentation/upgrading-midcom-from-2-4-to-2-6/
once you've achieved that, here's the continuation (also not entirely
complete):
http://www.midgard-project.org/documentation/upgrading_midcom_from_2-6_to_2-8/
But for this, you have to be able to access the migration exec methods,
so you have to use the correct midcom.php before starting.
Bye,
Andreas
2. How can I go about cleaning up the mess that I now have on my
hands ? Is there a way to uninstall MidCOM and
then do a clean install ?
With pear packages you have pear uninstall, but other stuff has to
be cleaned manually I guess (but I don't think it would interfere
with your install to keep the files around. I might be wrong,
though...)
That's what I was wondering about, will doing a pear uninstall be
sufficient ? In particular, is there stuff in the midgard database
itself that would need to be cleaned out ?
Below this reply is a list of all of the current midcom packages I
have installed. Would I want to remove and re-install ALL of them ?
Or remove them all and then use
datagard to do the re-install ?
Again, my experience with Midgard/MidCOM wizards was not the best so
far, instead I usually follow this:
http://blogs.nemein.com/people/piotras/view/midgard-1-8---pear-issues-on-debian-stable.html
for installation (it's a bit dated now, but mostly still valid). The
-f switch on the pear command line overwrites the installed package,
so you shouldn't have to uninstall them first manually.
Thanks, I'll give this a try.
Martin
Bye,
Andreas
3. Maybe the most important question of all: Will MidCOM
replicate all Midgard elements (pages, styles, snippets ) or
just MidCOM components ?
I tested it just briefly (I'll have to implement it for a site next
month, and I'm already having nightmares about that), but as far as
I can tell, everything is replicated.
That's a relief !!
Thanks very much for your help.
Martin
Bye, and good luck!
Andreas
Here's my list of installed packages:
Installed packages, channel pear.midcom-project.org:
====================================================
Package Version State
Javascript_protoToolkit 1.0.7 stable
Role_Mgdschema 1.0.0 stable
Role_Midgardelement 1.1.4 stable
Role_Midgardsql 1.0.0 stable
de_bitfolge_feedcreator 1.8.0 stable
de_linkm_sitemap 1.2.0 stable
fi_protie_navigation 1.2.0 stable
midcom 2.9.0beta1 beta
midcom_admin_babel 0.2.0 stable
midcom_admin_content 2.5.5 stable
midcom_admin_folder 1.3.0 stable
midcom_admin_help 1.1.0 stable
midcom_admin_settings 0.2.0 stable
midcom_admin_styleeditor 0.3.0 stable
midcom_admin_user 1.1.0 stable
midcom_helper_datamanager 2.6.0 stable
midcom_helper_datamanager2 1.1.1 stable
midcom_helper_dm2config 0.1.0 beta
midcom_helper_imagepopup 0.2.0 stable
midcom_helper_reflector 0.2.0 stable
midcom_helper_replicator 1.1.0 stable
midcom_helper_search 1.1.0 stable
midcom_helper_xml 1.1.0 stable
midgard_admin_acl 1.1.0 stable
midgard_admin_asgard 2.1.0 stable
midgard_admin_sitegroup 1.1.0 stable
midgard_admin_sitewizard 2.3.0 stable
net_nehmer_blog 1.6.0 stable
net_nehmer_buddylist 1.1.0 stable
net_nehmer_comments 1.1.0 stable
net_nehmer_markdown 1.1.0 stable
net_nehmer_static 1.1.1 stable
net_nemein_calendar 2.1.0 stable
net_nemein_favourites 1.1.0 stable
net_nemein_repeathandler 1.1.0 stable
net_nemein_rss 2.2.0 stable
net_nemein_tag 1.1.0 stable
no_bergfald_rcs 1.1.0 stable
org_openpsa_calendarwidget 2.2.0 stable
org_openpsa_contactwidget 2.1.0 stable
org_openpsa_core 2.1.0 stable
org_openpsa_helpers 2.1.0 stable
org_openpsa_httplib 1.1.0 stable
org_openpsa_mail 2.1.0 stable
org_openpsa_notifications 1.1.0 stable
org_openpsa_qbpager 1.1.0 stable
org_routamc_gallery 1.2.0 stable
org_routamc_photostream 1.2.0 stable
org_routamc_positioning 1.4.1 stable
stock_icons 1.0.0 stable
template_Howto 1.0.0 stable
template_Kubrick 1.0.4 stable
template_Midgard 1.0.1 stable
template_OpenPsa2 1.1.1 stable
template_SimpleGray 1.0.3 stable
------------------------------------------------------------------------
_______________________________________________
user mailing list
[email protected]
http://lists.midgard-project.org/mailman/listinfo/user
_______________________________________________
user mailing list
[email protected]
http://lists.midgard-project.org/mailman/listinfo/user
------------------------------------------------------------------------
_______________________________________________
user mailing list
[email protected]
http://lists.midgard-project.org/mailman/listinfo/user
begin:vcard
fn:Andreas Flack
n:Flack;Andreas
org:CONTENT CONTROL Berlin GbR
adr;dom:;;Ebertystr. 20;Berlin;Berlin;10249
email;internet:[EMAIL PROTECTED]
tel;work:+49 (0) 177 565 19 13
tel;fax:+49 (0) 30 639 018 64
x-mozilla-html:FALSE
url:http://www.contentcontrol-berlin.de
version:2.1
end:vcard
_______________________________________________
user mailing list
[email protected]
http://lists.midgard-project.org/mailman/listinfo/user
