Ok, shame on me. It turns out I had a typo in my staging_to_live script. I
fixed it and now it works fine ...
Bye, and thanks for the help,
Andreas
Am Mittwoch, 21. April 2004 14:48 schrieb Eero af Heurlin:
Hmm, it shouldn't touch topics at all, but it's easy to check, just copy
the dump
Thanks for the tip, approval finally works now. One problem remains, though:
When I move a topic, the change is not exported to the live db. Does this
have to do with the fact that I'm dumping the data without using -a?
Bye,
Andreas
Am Dienstag, 20. April 2004 20:40 schrieb Eero af Heurlin:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sonic wrote:
| Thanks for the tip, approval finally works now. One problem remains,
though:
| When I move a topic, the change is not exported to the live db. Does this
| have to do with the fact that I'm dumping the data without using -a?
|
It should
Ok, but what can I do to get the moved topic published? In aegir and on the
staging server, everything looks like it should, but the change isn't copied
to the live db. BTW: The same holds true for other changes to a topic. When I
edit a topic's description in aegir, the change isn't copied to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sonic wrote:
| Ok, but what can I do to get the moved topic published? In aegir and
on the
| staging server, everything looks like it should, but the change isn't
copied
| to the live db. BTW: The same holds true for other changes to a topic.
When I
|
I investigated the problem a little bit further and it seems that
clean_tag_simple($current_obj_data{sitegroup}) is called in line 84 and
$current_obj_data{sitegroup} is empty. I don't know why this happens, but
because of that, the unapproved article is not removed from the xml file. If
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sonic wrote:
| I investigated the problem a little bit further and it seems that
| clean_tag_simple($current_obj_data{sitegroup}) is called in line 84 and
| $current_obj_data{sitegroup} is empty. I don't know why this
happens, but
| because of that,
Hi!
Following Henrie's advice, I'm trying to set up replication with the help of
YAMP. I downloaded the whole thing from cvs and copied
downgrade_unapproved.pl and delete_expired.pl to /var/lib/aegir/bin. I then
modified repligard_staging_to_live.sh to use the new scripts. Everything is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sonic wrote:
|
| Following Henrie's advice, I'm trying to set up replication with the
help of
| YAMP. I downloaded the whole thing from cvs and copied
| downgrade_unapproved.pl and delete_expired.pl to /var/lib/aegir/bin. I
then
| modified
Thanks for the fast reply. Using iconv fixed the umlaut problem. As for
unapproved stuff getting published: I found out that there's an error when
the script runs (I tried it with a modified and unapproved article):
Use of uninitialized value in pattern match (m//) at /var/lib/aegir/bin/
The remove_unapproved script seems to work fine on
pages and articles but isn't working style and style
elements.
I use repligard's -m option (Create GUID information
for all resources).
-- Has anyone a clue, what I should do to make the
script work for styles, the xml contains both the
record
Hi,
I have started using midgard a while ago and i'm
running across some replication problems.
I have used the downgrade_unapproved.pl and found it
is not usefull for downgrading anything but unapproved
pages.
Right now I have started to look at YAMP and use its
remove_unapproved.pl script to
12 matches
Mail list logo
