Support Rules and Guidelines

So, until about a month ago, I was pretty happily using the relative url of the site skin files we had hosted in our ACP like so ;

/uploads/site/filename.png

& as postimage went down(Which a coadmin was using for some site images prior), I went to move those over to our hosting too...when I realized the urls had changed to files.jcink instead of being hosted on our actual url;Which in & of itself doesn't bother me url wise, but now I can't seem to use relative urls at all in the img tag(Which I liked to do to ensure it still worked on HTTPS & http for whoever was using which version of the site) & even if I just remove the https/http in front of it to let it resolve on its own, it gives me this;


Which isn't right, because I have the dynamic images activated too(& have doubled checked twice)



SO I guess my questions are;
-was file location when you host via ACP changed for a reason? I haven't seen an announcement about it but to be honest I might have missed it.
-Will relative url usage just never work now for them?
-Is it because the relative url doesn't work anymore that I'm getting that error or is there some other new setting I need to change?
-Am I just an idiot & it never worked in POSTS, perhaps, which is a valid answer.

This post has been edited by All Perspicacity: Apr 14 2018, 04:13 PM

QUOTE

-was file location when you host via ACP changed for a reason? I haven't seen an announcement about it but to be honest I might have missed it.

Yes, we want to serve all static content from 1 dns address. It should have no affect on serving the files and is actually unrelated to the issue you're having with the [img] tag. There was no announcement about it. The board was serving the urls via b1.jcink.com and we just updated it at some point -- I don't remember when this was, but it was months ago.

QUOTE

-Will relative url usage just never work now for them?

I'm going to look into why you can't use relative URLs with the image tag as it is an issue that doesn't relate to the file url changing. You should notice that if you use relative urls with HTML, it should be fine and works the same.

QUOTE

-Is it because the relative url doesn't work anymore that I'm getting that error or is there some other new setting I need to change?

I have actually never tried to link images this way via the [IMG] tag. So I do not know why it is complaining about it despite the dynamic images setting being turned off.

QUOTE

-Am I just an idiot, perhaps, which is a valid answer.

No, you are not.

Bless :Prayinghands:

It's not an emergency or anything, I just thought I'd ask since I was using relative urls so instinctively that it suddenly not working threw me off something serious.

Thank you!

How long has it not been working? We have not made any changes to the post system core recently at all, that is what's odd. But I am seeing the same issue here.

OK, I believe this has been patched. It's pecular though that you've been able to get it to work since this bit of code was doing it:

CODE

// Is it a legitimate image?    if (!preg_match( "/^(http|https|ftp):\/\//i", $url ) && $ibforums->vars['allow_dynamic_img'] != 1) {   $this->error = 'no_dynamic';   return $default;  }

But it didn't have the additional check to see if dynamic image URLs were enabled or not. I just added that now. No idea how that was working before. Either way it should be fixed now.

I am also sure you might already know but wanted to mention it anyway: relative URLs are not compatible with domain names, and that is regardless of https or not. They should work on the jcink url.

All Perspicacity try it now with the dynamic images option enabled and see if it works.

Works perfectly, thank you!

This topic has been solved. If you need anymore help please post a new thread. Thanks for choosing Jcink services.