http://permalink.gmane.org/gmane.comp.web.midgard.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.web.midgard.user/8045 phpize comes with php4 devel packages from your distributions. /Johan On Wed, 2006-03-08 at 08:52 +0000, Reid Lai wrote: Johan Bernhardsson 2006-03-08T17:38:24 http://permalink.gmane.org/gmane.comp.web.midgard.user/8044 Dear All, I am new to php and midgard and installating Midgard 1.7.4. When I run ./mkall in order to configure new installation of midgard-php4- 1.7.4, there is an error as below: [midgard< at >tts midgard-php4-1.7.4]$ ./mkall ./mkall: line 20: phpize: command not found ./mkall: line 34: ./configure: No such file or directory make: *** No targets specified and no makefile found. Stop. make: *** No rule to make target `install'. Stop. I don't have idea what 'phpize' is. Anyone can give me some information and hint. Thanks. Reid Lai 2006-03-08T08:52:29 http://permalink.gmane.org/gmane.comp.web.midgard.user/8043 Hi, I'm curious to know why the binary download for Mac OS X is a Bzip2 compressed Disk Image file. Why isn't it simply a Disk Image file? http://www.midgard-project.org/osx/installer/Midgard.dmg.bz2 Cheers, Christiaan Christiaan Briggs 2006-03-07T16:53:35 http://permalink.gmane.org/gmane.comp.web.midgard.user/8042 Hello, I'm interested on webalizer stats ..... --- Henri Bergius <henri.bergius-ZpG/hlzQTXLQT0dZR+AlfA< at >public.gmane.org> a écrit : -------------------------------------------------------------------- --------------------------------------------------------------------- --------------------------------------------------------------------- iD8DBQFD8H1ONkT8k497k9IRAo76AJ9aSz7WMj7TjCO6oVRt+0gewbVQ3wCgzNf1 --------------------------------------------------------------------- ___________________________________________________________________________ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com Koffi Marcel 2006-03-07T14:37:35 http://permalink.gmane.org/gmane.comp.web.midgard.user/8041 Hi, On 3/2/06, Sonic <sonic< at >sonicpictures.de> wrote: OK, I'll take a look at this. Can you file an issue for this either in the Midgard issue tracker on tigris or in the Exorcist issue tracker on sourceforge? BR, Jukka Zitting -- Yukatan - http://yukatan.fi/ - info< at >yukatan.fi Software craftsmanship, JCR consulting, and Java development Jukka Zitting 2006-03-02T11:34:13 http://permalink.gmane.org/gmane.comp.web.midgard.user/8040 Am Donnerstag, 2. März 2006 10:00 schrieb Jukka Zitting: Hi! Thanks for the fast reply! Yes, I'm not replicating the entire db, just Styles and Snippets, and I've deleted a lot of User accounts from the staging server after the last complete synchronisation. Needless to say, these are still needed on the live server, so being able to restrict deletes to certain classes would be most helpful! Bye, Andreas Sonic 2006-03-02T10:37:21 http://permalink.gmane.org/gmane.comp.web.midgard.user/8039 Hi, On 3/2/06, Sonic <sonic< at >sonicpictures.de> wrote: Yes, with some restrictions. See the warning below. Are you are using a XSLT selection to only replicate the mgd:midgard_style content? The delete information is exported as separate mgd:delete elements at the end of the XML export, so you'll be able to replicate the deletions if you add something like <xsl:apply-templates select="mgd:delete"/> to your stylesheet. WARNING: The exported deletions contain *only* the deleted GUID, so there is currently no way to restrict the deletions to just one object class (like styles or style elements) or object tree (like some specific style A). The class information would be possible to include, but not the tree information because of the way Midgard currently handles parent links. BR, Jukka Zitting -- Yukatan - http://yukatan.fi/ - info< at >yukatan.fi Software craftsmanship, JCR consulting, and Java development Jukka Zitting 2006-03-02T09:00:59 http://permalink.gmane.org/gmane.comp.web.midgard.user/8038 Hi! Just a quick question: Does Exorcist have support for exporting deletes already? If no: Is this planned for the future? If yes: It doesn't work for me. I deleted one Style Element on the staging server, ran Exorcist and still had it on my live server afterwards. Do I have to make some special configuration for this to work? Bye, Andreas Sonic 2006-03-02T02:09:22 http://permalink.gmane.org/gmane.comp.web.midgard.user/8037 The PHP implementation of Markdown will be smarter about this when we upgrade to the version shipping with MidCOM 2.5... http://www.michelf.com/projects/php-markdown/extra/#em /Bergie Henri Bergius Consultant Partner, Nemein henri.bergius-ZpG/hlzQTXLQT0dZR+AlfA< at >public.gmane.org Midgard CMS www.midgard-project.org Henri Bergius 2006-03-01T18:54:01 http://permalink.gmane.org/gmane.comp.web.midgard.user/8036 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, - --Arttu Manninen wrote on 2006-03-01 12:59: Yeah, this is a well-known problem nowadays, but not trivial to fix because, as you say, these cases are not exactly easy to spot. When we start fixing this, I recommend some different approach. Instead of masking the underscores and thus having the function name set in normal type, quote it using backticks, like this: "some text with `a_function_name()` being mentioned" This will have the "a_function_name()" piece set in a monospaced font, the common way to denote any programming constructs within normal text. See MRFC 26 for a few examples how this'll look. Live long and Prosper! Torben Nehmer - -- Torben Nehmer, Guenzburg, Bavaria, Germany http://www.nathan-syntronics.de, mailto:torben-7IYgsjUNgN6sTnJN9+BGXg< at >public.gmane.org PGP Public Key: https://www.link-m.de/pgp/t.nehmer.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev. Torben Nehmer 2006-03-01T12:21:24 http://permalink.gmane.org/gmane.comp.web.midgard.user/8035 Hi, Andreas! This is both a bug that came along, when old 'de.linkm.taviewer' documentation was ported to 'net.nemein.wiki' documentation, and a possible mistake of document writers, I think. Wiki formatting sees underscore (_) as a start of italics unless an escape character has been used with it (\_). This means that get_current_leaf() will display as get<i>current</i>leaf(). Functions and methods are easy to write wrong and when reading your own text, italics are still relatively easy to miss in a long text. I have been correcting every time I see these mistakes. I have been editing loads of old mgd_*** functions, but I haven't caught them all. The same goes with other parts of the documentation. Whenever you come across with similar mistakes, please send me the url and I'll be correcting it. Arttu Manninen 2006-03-01T11:59:26 http://permalink.gmane.org/gmane.comp.web.midgard.user/8034 Hi! I've noticed this several times now and thought I'd post ist to the list: There seems to de a formatting problem in Midgard's documentation pages, which has the effect that underscores are not displayed, but converted to <em> tags. This might be a feature, but in the case of class or method names, it's a bug. For example get_current_leaf() is displayed as getcurrentleaf() where "current" is written in italics. See http://www.midgard-project.org/documentation/concepts-midcom-specs-components-styleguide/ Section Naming conventions - Classes for more examples. Bye, Andreas Sonic 2006-03-01T11:47:23 http://permalink.gmane.org/gmane.comp.web.midgard.user/8033 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings! It seems the MidCOM PEAR channel (pear.midcom-project.org) doesn't work with the latest PEAR release. If you encounter this, downgrade by running # pear upgrade -f PEAR-1.4.6 Henri Bergius Consultant Partner, Nemein henri.bergius-ZpG/hlzQTXLQT0dZR+AlfA< at >public.gmane.org Midgard CMS www.midgard-project.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEBBnaNkT8k497k9IRAlizAKCb5C99EMdpX7/6RZOq7iijwKHubQCeLZ1V 3e77Kmc+BmjzKs6vmg/hH7Y= =kQEj -----END PGP SIGNATURE----- Henri Bergius 2006-02-28T09:37:29 http://permalink.gmane.org/gmane.comp.web.midgard.user/8032 Hi, I got two sites within one SG. I got a topic trees like that: site-one-root { galleries { gallery1 { photos } gallery2 { photos } } } site-two-root { galleries { gallery1 { photos } gallery3 { photos } } } As you can see gallery1 should be shared between two sites. I don't want to make copies to avoid multiplying files and using too much of a disk space. Is it possible to somehow symlink n.s.photos topics? Solt Marcin Sołtysiak 2006-02-24T18:59:40 http://permalink.gmane.org/gmane.comp.web.midgard.user/8031 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Feb 24, 2006, at 12:02, Tarjei Huse wrote: We could create another custom role for this, yes. Even after midgard- schema table creation this could be useful for adding indexes, etc. Any preferences on the location? Maybe config/database.sql ? /Bergie Henri Bergius Consultant Partner, Nemein henri.bergius-ZpG/hlzQTXLQT0dZR+AlfA< at >public.gmane.org Midgard CMS www.midgard-project.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFD/toyNkT8k497k9IRAnMeAJ9Es1a1ViSViMDNKoxMvNZlSpaLxACfVwh5 NIfw9UGDPI1UUE00W2uINcg= =6YC3 -----END PGP SIGNATURE----- Henri Bergius 2006-02-24T10:04:33 http://permalink.gmane.org/gmane.comp.web.midgard.user/8030 Bergie, could we have a midgard_sql directory configuration item? Take a look on the testhost. The pearsetup there is fairly complete. I think you'll probably see you're missing some pear commands. Tarjei Tarjei Huse 2006-02-24T10:02:00 http://permalink.gmane.org/gmane.comp.web.midgard.user/8029 Absolutely not. The same way as dg handles it now. But pearized MidCOM is not going to be included in some 1.7 release. If we need this , we need to move dg from HEAD to 1-7 branch. 1. Tables create and update. a) Use midgard-schema b) DG automagically handles sql files placed in sql/update subdirectory. 2. I have no idea about static dirs and pear. 3. DG in HEAD supports pear and pearized midcom. This is initial as I still do not know what packages should be installed. Piotras Piotras 2006-02-24T09:57:47 http://permalink.gmane.org/gmane.comp.web.midgard.user/8028 Hi, with MidCOM 2.6 comming along nicely, I'm starting to wonder how poeple are planning to get the midgard tables updated for the extra MidCOM schemas. As I see it there are a few options: 1. Release MidCOM with 1.8 only. -> Risky as we do not know when 1.8 will be out. 2. Release Midcom for 1.7 with a simple update script as a stopgap measure. Item (2) raises tow new questions: a) Should this release be done with pear? b) If if should be done with pear, how should we package and run the tableupdates? I'm wondering as I'm trying to get the pear installations running on the testbox and I see this and the issues on static dirs as the main problems at the moment. Regards, Tarjei tarjei 2006-02-24T09:08:14 http://permalink.gmane.org/gmane.comp.web.midgard.user/8027 Exorcist setup was correct. The only problem was image serving, and that is now solved :-) # chmod -R a+rx /var/lib/midgard/blobs /Bergie Henri Bergius Consultant Partner, Nemein henri.bergius-ZpG/hlzQTXLQT0dZR+AlfA< at >public.gmane.org Midgard CMS www.midgard-project.org Henri Bergius 2006-02-22T21:05:53 http://permalink.gmane.org/gmane.comp.web.midgard.user/8026 Lodz, February 21st 2006 -- The Midgard Project has released stable release version 1.7.4 of the Midgard Open Source Content Management System. Midgard's 1.7 branch is a major overhaul of the whole Content Management System. Besides the stable and mature Content Management features of first generation Midgard, it also ships a preview version of second generation Midgard capabilities, allowing developers to have a glimpse at the new day of Midgard2. 1.7.4 is maintenance and bugfix release. Midgard 1.7 for end users For the end users, Midgard 1.7 brings the mature MidCOM Content Management interface version 2.4, and the new Midgard Site Wizard for easy website creation. The new MidCOM has been developed with performance in mind, and has been moved from the Midgard database into the file system. MidCOM also includes a new output caching system. In addition to performance, MidCOM's new features include a full- fledged metadata management system and integrated content search using Ap Piotras 2006-02-21T09:50:02 http://permalink.gmane.org/gmane.comp.web.midgard.user/8025 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, - --Tarjei Huse wrote on 2006-02-20 14:39: No. Live long and Prosper! Torben Nehmer - -- Torben Nehmer, Guenzburg, Bavaria, Germany http://www.nathan-syntronics.de, mailto:torben-7IYgsjUNgN6sTnJN9+BGXg< at >public.gmane.org PGP Public Key: https://www.link-m.de/pgp/t.nehmer.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFD+cbTJPh4Kn6d5FYRAoLkAJ9JVxh3cDDtw/njvjmOtSxsHr33UACfVFVx wLaKXd/EsSyF4s8hRDgDXVk= =GAjm -----END PGP SIGNATURE----- Torben Nehmer 2006-02-20T13:40:35 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.web.midgard.user