Thread

situation:

I migrated another site from Pmachine to EE (latest build). Imported entries (using old import from build 1.5.0, or else it doesn’t work!), and everything went okay.

i’ve been using pmcode like this in my old pmachine’s body:

[url=/comments.php?id…]link[/url]

this way links had “target=_self” (no browser opened).

When I wanted to open a browser I simple used “http” before it like this:

[url=http://site.com/comments.php?id…]link[/url]

for some weird (?) reason it worked out perfectly, and a new browser opened (target=_blank).

problem: After migrating to EE, all links in the body without the “http://site.com” didn’t work anymore. And all links are going to the same window (unless I change base target of that table/div of course)

Any idea why I can’t use the first option anymore?

Thanks

In truth- I’m not sure why it worked that way with pMachine.  What did the actual urls look like when pm opened them in a new window.  That might give us a good hint.  But with EE, I wouldn’t expect the above to work unless you were using an ?url= in it.  I THINK that would work.  But not like I understand pm did.

well, actual urls looked the same, but the relative urls worked also because pmachine added the domain address in front of it.

I don’t know how to explain better, but in this example:

[url=/comments.php?id=0]link[/url]

..the url on the site looked normal: http://domain.com/comments.php?id=0

In EE on the other hand, the actual url on the site looks like this (when using the same format as above):

http:///comments.php?id=0

It domain is missing..

You might have a look at this post, as I think you’re asking about that.

hm, I don’t get it 😊

I always have the problem with the relative urls, so alle my urls were wrong from the orignal body. I had to use the “Find and replace” tool for adding the domain in all entries…

But I would prefer using relative! (relative is always better I guess). Any way to fix this?

You would need to use straight HTML to use relative links - using relative links was a bug that was fixed, as per that post.  It’s possible you could create a plugin to parse out links in your preferred format, as well.

hm, k. Thanks!