Andreas Flack wrote:
Martin Gottlieb schrieb:



Henri Bergius wrote:
Hi,

On Feb 19, 2008 11:38 PM, Martin Gottlieb <[EMAIL PROTECTED]> wrote:
Where should I expect to find midcom.admin.content ?  Is it a plain
file-system file or a "magic" midgard URL living
in the midgard database ?  What package is it included in ?

Which MidCOM version?

midcom.admin.content was used in MidCOM's from 0.1 to 2.4, but then
replaced with the combination of midcom.admin.folder (on-site folder
management), midgard.admin.asgard (full admin UI) and components
providing their own admin UIs.

/Henri

Well that is interesting ! I'm using MidCOM 2.8, but I apparently have some remnants of an older
version left behind, based on what you are saying.

The full story is that I started with a 1.7.6 Midgard system, running MidCOM 2.4. I copied the database to a new server running Midgard 1.8.6 (MidCOM 2.6 ) and updated it in datagard. I then moved on to trying to set up replication. After being told that I needed MidCOM 2.8 for this, I first attempted to install it from the svn repository, based on one posting that I had found. I was then told that it
could be downloaded via pear using the beta version, which I tried.

It does not appear than any of my attempts have been successful. So my questions are:

1. Is going to http://mysite.com/midgard/midcom-admin/ the correct way to determine if the install is good ?

midcom-admin doesn't exist any more AFAIK, I would suggest a two-level approach: First check mysite/spider-admin, this will tell you if Midgard is running ok, next try mysite/__mfa/asgard/, which should give you access to the new management interface. mysite/midcom-exec-midcom/config-test.php can also be informative, it tests some settings needed by MidCOM
/spider-admin comes up just fine as does the site I'm trying to replicate in the first place. Both __mfa/asgard/ and midcom-exec-midcom/config-test.php are returning 404s.


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 ?


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

Reply via email to