MLP: The Next Generation

dl33 · 2009-03-18 00:35:24

Ah, took me some time to see that the thread had “moved”: I posted a question in the old one and only saw today that the thread had been closed. Since I am a bit stuck on whom to ask about this, I’ll simply copy/paste from the old thread if you don’t mind:

Oh, and I am happy to provide German and Dutch translations for the MLP. I’ll upload them to TXPForge over the next couple of days…

Moved back to where it came from;-)

Last edited by dl33 (2009-03-18 00:56:40)

els · 2009-03-18 00:46:44

dl33 wrote:

Ah, took me some time to see that the thread had “moved”: I posted a question in the old one and only saw today that the thread had been closed.

Hi, sorry about the closed thread, I don’t think this thread should be the replacement, and anyway there should have been a notice in the old thread. I’m trying to find out how to get it re-opened ;)

And I have been thinking about your post, just need a bit more time ;) I’m sure there is a way to do what you want.

A Dutch translation is available, German would be welcome!

maniqui · 2009-03-18 01:01:04

@dl33

What about cloning the article and trying a redirect (from cloned articles URL to original article) instead of a rewrite?

Or, if that doesn’t work, you may want to try using txp:article_custom + txp:if_article_id or even txp:l10n_if_lang.
You put all the comment tags inside the txp:article_custom (which will have @id=“XX”, where XX is the id of the original (English) article.
Although, I’m not sure if that kind of magic works. I don’t know if TXP comments form works by submitting some hidden value to tell TXP to which article the comment belongs or by looking at the URL from where the comment form was submitten (if that’s the case, then it probably won’t work).

But you tell us!

maniqui · 2009-03-18 01:11:17

In the Renditions tab, look at the ID column.
Look for the ID of your English article.
Then use that ID in article_custom.

maniqui · 2009-03-18 01:32:53

dl33 wrote:

get id of english version of displayed article->

Not current possible, AFAIK. I’ve requested that (to have a way to access the data of other rendition for this article, so to get article id, the value of custom fields, etc) some time ago. In other words, to share some data/fields across renditions.
Check this post and also the one linked on that post (well, this).

I hope this could be added in a future release.

maniqui · 2009-03-18 01:36:23

@dll33,
in the meanwhile, probably the best way is by storing the ID of the original article on a custom field for each rendition.

So then, you could do something like this (pseudo code):

if lang = en
    ...some comment form tags...
else
    <txp:article_custom id='<txp:custom_field name="original_article_id" />'>
    ...some comment form tags...
    </txp:article_custom>

tom1 · 2009-03-20 10:08:00

Whats the situation with this plugin support? i tried to download fixed .zip (MLP Pack 0.9.11 GP) from the link in this topic, but no host found. Also checked from txpforge.org but that zip isnt available for download from there either..

I wouldn’t liketo change back to previous version of txp just to get mlp to work!

els · 2009-03-20 10:25:20

tom1

Thanks for reporting this, I’ll let Graeme know the download doesn’t work. I’ve put my copy of the zip temporarily ~~here~~. (edit: removed, download link on txpforge.org is fixed.)

Last edited by els (2009-03-20 17:12:32)

graeme · 2009-03-20 11:16:12

Els wrote:

I’ll let Graeme know the download doesn’t work

Fixed!

els · 2009-03-20 17:09:05

graeme wrote:

Fixed!

Thank you :)

tom1 · 2009-03-21 11:29:20

thanks for quick reply! its good to see that mlp is still supported :)

nigromontanus · 2010-04-01 15:58:05

It seems txpforge.org is down…i am getting 503’s for the last three days…is there any way to acquire a copy of MLP 0.9.13 (if that is the latest version compatible to TXP 4.2.0) at the moment?

I put great expectations into that version of MLP, since MLP 0.9.11 in combination with TXP 4.2.0 produced some nasty charlie foxtrotts (especially with the design…apparently the l10n-module did not like my CSS and disabled it, so the site appeared in that shiny Times-New-Roman-back-to-1994-look when l10n was active).

Caveat I: I am testing this currently under MAMP, -any chance the problem is rooted there?
Caveat II: Consider me a complete greenhorn but quick learner in all matters TXP, it is quite possible i overlooked something.

Textpattern CMS

Textpattern CMS support forum

#13 2009-03-18 00:35:24

Re: MLP: The Next Generation

#14 2009-03-18 00:46:44

Re: MLP: The Next Generation

#15 2009-03-18 01:01:04

Re: MLP: The Next Generation

#16 2009-03-18 01:11:17

Re: MLP: The Next Generation

#17 2009-03-18 01:32:53

Re: MLP: The Next Generation

#18 2009-03-18 01:36:23

Re: MLP: The Next Generation

#19 2009-03-20 10:08:00

Re: MLP: The Next Generation

#20 2009-03-20 10:25:20

Re: MLP: The Next Generation

#21 2009-03-20 11:16:12

Re: MLP: The Next Generation

#22 2009-03-20 17:09:05

Re: MLP: The Next Generation

#23 2009-03-21 11:29:20

Re: MLP: The Next Generation

#24 2010-04-01 15:58:05

Re: MLP: The Next Generation

Board footer