Can you post the xml part of this content after export? What tags are these line breaks?
I assume the content displays normally when seen on your PivotX site?
<content:encoded><![CDATA[Maarten op de Mixfreaks mailinglist schreef; > Hou jij van klassiek? Misschien niet, maar je voorouders zullen je zeggen > dat dat de enige muziek is die er bestaat en rock 'n' roll of weet ik veel > welke andere muziekstroming niets! Het gaat mij om iets heel anders, namelijk dat men bij de radio en in de detailhandel nogal geneigd is om op safe te spelen. Tot aan ongeveer 1995 was dat echt beduidend minder het geval en dat heeft niks met mijn leeftijd te maken. De platenzaken die voorheen nog wel eens een plaat/CD hadden liggen waarvan bekend was dattie NIET bij voorbaat de hitparade in zou komen durven dat niet meer(?). Mijn muzieksmaak is ècht niet die van een old-timer of gek, en ik kan heel erg meekomen in veel nieuwe muziek die wel te koop ligt, maar BINNEN die genres neemt men geen enkel risico meer. Er liggen bijv. geen import-plaatjes meer in main-stream winkels. Vroeger lagen ze zelfs nog in V&D. Ander probleem vind ik dat de platenzaak waar ik dan nog wèl kleine labels en import kan vinden weer op zo'n overdreven manier
Not too unexpected; Debian is too slow releasing updates, let alone backports to older OS versions, like debian 6 (squeeze) or older. So with them old OS-es you're stuck with old openssl crap through apt-get update, and standard install from source will *not* update a previous apt-get installed openssl! Still want to update to 1.0.1g or later? Here's how it *does* work: Check the link for the version that says <a href="https://www.openssl.org/source/">[LATEST] over here</a>. Currently that means you need to do <code># wget https://www.openssl.org/source/openssl-1.0.1g.tar.gz # tar xfz openssl-*.tar.gz # cd openssl-* # ./config --prefix=/usr zlib-dynamic --openssldir=/etc/ssl shared enable-ec_nistp_64_gcc_128 </code> It then asks you to do make depend, which you should, and you follow with the usual: <code># make depend # make # make install</code> and then you can check the version that's running on your server with <code>openssl version</code> and if it says: <code>OpenSSL 1.0.1g 7 Apr 2014</code> you're safe and sound in Snowden-land. This also works for Ubuntu 8 (hardy) by the way. Be sure to reboot your server after that, renew your server certificates, ask (or better yet FORCE) your users to change their passwords. Of course, you've now gone to source for this package. And trying <code>apt-get remove openssl</code> will result in sheer dependency hell. Forget about letting apt manage openssl in any way or manner. dovecot, nginx, postfix etc. should all still work fine through apt with backports and such. They'll use the right openssl libraries now.]]></content:encoded>
<p>Not too unexpected; Debian is too slow releasing updates, let alone backports to older OS versions, like debian 6 (squeeze) or older.<br /> <br /> So with them old OS-es you're stuck with old openssl crap through apt-get update, and standard install from source will *not* update a previous apt-get installed openssl!<br /> Still want to update to 1.0.1g or later? Here's how it *does* work:<br /> Check the link for the version that says <a href="https://www.openssl.org/source/">[LATEST] over here</a>. Currently that means you need to do<br /> <code># wget https://www.openssl.org/source/openssl-1.0.1g.tar.gz<br /> # tar xfz openssl-*.tar.gz<br /> # cd openssl-*<br /> # ./config --prefix=/usr zlib-dynamic --openssldir=/etc/ssl shared enable-ec_nistp_64_gcc_128<br /> </code><br /> It then asks you to do make depend, which you should, and you follow with the usual:<br /> <code># make depend<br /> # make<br /> # make install</code><br /> and then you can check the version that's running on your server with <code>openssl version</code> and if it says: <code>OpenSSL 1.0.1g 7 Apr 2014</code><br /> you're safe and sound in Snowden-land. This also works for Ubuntu 8 (hardy) by the way.<br /> <br /> Be sure to reboot your server after that, renew your server certificates, ask (or better yet FORCE) your users to change their passwords.<br /> <br /> Of course, you've now gone to source for this package. And trying <code>apt-get remove openssl</code> will result in sheer dependency hell. Forget about letting apt manage openssl in any way or manner. dovecot, nginx, postfix etc. should all still work fine through apt with backports and such. They'll use the right openssl libraries now.</p>
<p>Page breaks:<br />This<br />and<br />that</p>
<p>Page breaks:<br />This<br />and<br />that</p>
Harm10 wrote:I am sorry to say that I cannot reproduce your problem.
In my introduction is this
- Code: Select all
<p>Page breaks:<br />This<br />and<br />that</p>
and in my export is this:
- Code: Select all
<p>Page breaks:<br />This<br />and<br />that</p>
So exactly the same.
I am on PivotX 2.3.10.
jult wrote:By the way, that can't be true. I mean, the export has: <content:encoded><![CDATA[ and no <p> in it. What do you use to export with?
Users browsing this forum: No registered users and 3 guests