The stupidity is absolutely relative
-
Okay so, like, y'all heard of this thing called Masterpages, right? It's SOO fucking awesome. It's like you write a page, but then that page is kinda like a template for all other pages. It's SUPER COOL! You can even do stuff like put, say, a hyperlink on that page-- AND EVERY OTHER PAGE WILL AUTOMATICALLY GET THAT HYPERLINK!
So, like, some coder back in 2008 did just that, right? Put a few hyperlinks. Cool cool cool.
But then oh shit bummer-- a page in the website that uses the masterpage-- and I mean, this is serious code red all hands on deck problems yo-- that page is in a subfolder. Right, so it's like \SubFolder\OhNo.aspx!
NOW NONE OF THE HYPERLINKS WORK! Because the hyperlink is all "Hey, I'm a hyperlink to CoolPageOne.aspx", and it's l'il buddy is also just fucking around going "I'm a hyperlink to CoolPageTwo.aspx".
BUT THERE IS NO \SubFolder\CoolPageOne.aspx.
None. None. None!
NONE!
But me, Imma looking at the codes, and I can see it. I can see the solution that was graced from upon high unto us mortals. You are going to totally shits all yourselves with the brilliance! I mean, you can probably see it from where you sit and think and eat. Right, you can see it?
What do you do when you have hyperlinks in a single, central location that break like alls I just described right up a scrolls or two? The answer should be ABSOLUTELY obvious.
I'd use spoiler tags to hide the brilliance until you worked it out yourselves (you wouldn't hahaha it's okay). Whatcha be doing is this: You go around and identify ALL the pages that get mistargetted. I'll call them like I did before CoolPageOne.aspx, CoolPageTwo.aspx-- and so on (it's cannon because I used the same name). Okay, you find all of those pages--
AND YOU COPY THEM INTO \SubFolder!
Fixed. Fixed, motherfucker yes, fixed! The hyperlinks Just. Fucking. Work!
HAHAHAHAHAHAHAHAHAHAAHAH!!11!!MONDAY!AND!ALREADY!THIS!SHIT!!!!twelve
-
The logical conclusion would be to put your entire website into the subfolder.
-
No no NO, that's NOT how you fix this! The right way to do this is to copy the entire website for each sub folder, edit the master page for each copy so that the links point to the correct sub folder, then when you want to load a page from a sub folder just redirect the user to the correct copy. Now THAT is elegant!
@Lorne Kates said:
Filed under: ...Fuck you.
Fuck you too :)
-
I tried to have Google translate that for me, but they don't seem to have a ranting dumbass to English option.
-
WRONG.
What you want is some secure mediation through frames.
-
OK, now the important question: how did you avoid assault charges when finding a teammate did what you describe?
-
@taustin said:
I tried to have Google translate that for me, but they don't seem to have a ranting dumbass to English option.
That option's still in Beta.
-
@boomzilla said:
WRONG.
What you want is some secure mediation through frames.
Oh, man, just take a photo of those pages...
-
@Lorne Kates said:
@taustin said:
I tried to have Google translate that for me, but they don't seem to have a ranting dumbass to English option.
That option's still in Beta.
Wait, I forget my Google terminology.. is "Beta" "has been out in production for half a decade but still isn't profitable" or is it "not yet cancelled"?
-
@Lorne Kates said:
What do you do when you have hyperlinks in a single, central location that break like alls I just described right up a scrolls or two? The answer should be ABSOLUTELY obvious.
I love that you are alluding to fixing this with absolute URLs, when in fact you should be using Control.ResolveUrl, Control.GetRouteUrl, etc. for ASP.NET WebForms or UrlHelper.Content, UrlHelper.Action, etc. for ASP.NET MVC…
-
@Ragnax said:
I love that you are alluding to fixing this with absolute URLs, when in fact you should be using Control.ResolveUrl, Control.GetRouteUrl, etc. for ASP.NET WebForms or UrlHelper.Content, UrlHelper.Action, etc. for ASP.NET MVC…
Guess what all of those resolve to...
/HereIsAHint.aspx
-
@Lorne Kates said:
@Ragnax said:
I love that you are alluding to fixing this with absolute URLs, when in fact you should be using Control.ResolveUrl, Control.GetRouteUrl, etc. for ASP.NET WebForms or UrlHelper.Content, UrlHelper.Action, etc. for ASP.NET MVC…
Guess what all of those resolve to...
/HereIsAHint.aspx
Cute. Now guess what those should resolve to when I host an application in a /Virtual/Folder/…
/Virtual/Folder/GetAClue.aspx
-
@locallunatic said:
OK, now the important question: how did you avoid assault charges when finding a teammate did what you describe?
They don't generally co-charge assault and murder.
-
@morbiuswilters said:
Wait, I forget my Google terminology.. is "Beta" "has been out in production for half a decade but still isn't profitable" or is it "not yet cancelled"?
Both, generally.
Also, when I started reading this thread, I thought it was going to be about people from the south-east of the United States and their incestual relationships. I was disappointed.
-
@Ragnax said:
Cute. Now guess what those should resolve to when I host an application in a /Virtual/Folder/…
/Virtual/Folder/GetAClue.aspx
-
@drurowin said:
@locallunatic said:
OK, now the important question: how did you avoid assault charges when finding a teammate did what you describe?
They don't generally co-charge assault and murder.
It depends. Regardless, you guys probably mean "battery" and not "assault". Assault is just the threat or intimation of violence.
-
@morbiuswilters said:
It depends. Regardless, you guys probably mean "battery" and not "assault". Assault is just the threat or intimation of violence.
Eh, makes sense. I'm a Lisp evangelist, not a lawyer. Not similar at all, even though they're right next to each other on the Department of Labor job classifications.
-
@Lorne Kates said:
@Ragnax said:
Cute. Now guess what those should resolve to when I host an application in a /Virtual/Folder/…
/Virtual/Folder/GetAClue.aspx
Way to miss the point; you can't create a static rooted URL, because virtual folders imply you have to sort out the dynamic nature of the root. That's where those methods for resolving URLs come into play: "~/Foo.aspx" could be resolved to "/Foo.aspx" when the application is not deployed to a virtual folder, it could be resolved to "/Bar/Foo.aspx" when it is deployed to a virtual folder "Bar", or it could be resolved to any other rooted URL. However; you never have the actual fully rooted URL in your project. At best you have an application root-relative virtual path...
-
@morbiuswilters said:
@drurowin said:
It depends. Regardless, you guys probably mean "battery" and not "assault". Assault is just the threat or intimation of violence.@locallunatic said:
OK, now the important question: how did you avoid assault charges when finding a teammate did what you describe?
They don't generally co-charge assault and murder.
The workplace has too many witnesses to do more than threaten.
-
@locallunatic said:
OK, now the important question: how did you avoid assault charges when finding a teammate did what you describe?
Make sure the body is never ever ever found.
-
@locallunatic said:
The workplace has too many witnesses to do more than threaten.
Who said anything about the workplace? See, the best revenge isn't killing someone, it's kidnapping them, shooting them full of LSD and scopolamine, murdering their loved ones and then arranging the evidence so it looks like they did it. Then they think they had a psychotic break and killed everyone they care about. That way, their conscience does the work of tormenting them for you, for the rest of their life.
-
@morbiuswilters said:
@locallunatic said:
The workplace has too many witnesses to do more than threaten.
Who said anything about the workplace? See, the best revenge isn't killing someone, it's kidnapping them, shooting them full of LSD and scopolamine, murdering their loved ones and then arranging the evidence so it looks like they did it. Then they think they had a psychotic break and killed everyone they care about. That way, their conscience does the work of tormenting them for you, for the rest of their life.
You've given this altogether too much thought, haven't you. ;-)
-
@Ragnax said:
@morbiuswilters said:
@locallunatic said:
The workplace has too many witnesses to do more than threaten.
Who said anything about the workplace? See, the best revenge isn't killing someone, it's kidnapping them, shooting them full of LSD and scopolamine, murdering their loved ones and then arranging the evidence so it looks like they did it. Then they think they had a psychotic break and killed everyone they care about. That way, their conscience does the work of tormenting them for you, for the rest of their life.
You've given this altogether too much thought, haven't you. ;-)
Yes... thought....
-
@morbiuswilters said:
@Ragnax said:
@morbiuswilters said:
@locallunatic said:
The workplace has too many witnesses to do more than threaten.
Who said anything about the workplace? See, the best revenge isn't killing someone, it's kidnapping them, shooting them full of LSD and scopolamine, murdering their loved ones and then arranging the evidence so it looks like they did it. Then they think they had a psychotic break and killed everyone they care about. That way, their conscience does the work of tormenting them for you, for the rest of their life.
You've given this altogether too much thought, haven't you. ;-)
Yes... thought....
Oh, so you're that morbs... Er... uh... look who's not ratting out your location to the FBI!
-
Why is everyone assuming 1 File ⇔ 1 Page? Are you telling me there's a file named 323422.aspx that contains all the code for Community Server's layout?
-
@Ben L. said:
Are you telling me there's a file named 323422.aspx that contains all the code for Community Server's layout?
Are you telling me there's not? This is CS we're talking about..
-
@morbiuswilters said:
@Ben L. said:
Are you telling me there's a file named 323422.aspx that contains all the code for Community Server's layout?
Are you telling me there's not? This is CS we're talking about..
You mean this discussion was pre-generated by Community Server's developers and shipped with every installation of CS and just disabled in the settings?
Come to think of it, that sounds like what they would do.
-
@Ben L. said:
You mean this discussion was pre-generated by Community Server's developers and shipped with every installation of CS and just disabled in the settings?
The really eerie thing is they knew you were going to say that and hard-coded it into the aspx many years ago.
-
@morbiuswilters said:
@Ben L. said:
You mean this discussion was pre-generated by Community Server's developers and shipped with every installation of CS and just disabled in the settings?
The really eerie thing is they knew you were going to say that and hard-coded it into the aspx many years ago.
So...the extra backspaces are just them nudging you when you start writing the wrong post?
I always associated more of a Charles Manson style psycho than Hari Seldon when I thought about the CS developers. I guess there's no reason they can't be both.
-
@boomzilla said:
@morbiuswilters said:
@Ben L. said:
You mean this discussion was pre-generated by Community Server's developers and shipped with every installation of CS and just disabled in the settings?
The really eerie thing is they knew you were going to say that and hard-coded it into the aspx many years ago.
So...the extra backspaces are just them nudging you when you start writing the wrong post?
I always associated more of a Charles Manson style psycho than Hari Seldon when I thought about the CS developers. I guess there's no reason they can't be both.
This whole conversation was accurately predicted by the Community Server team back wombat but sometimes I just use MySQL
-
@Lorne Kates said:
Okay so, like, y'all heard of this thing called Masterpages, right? It's SOO fucking awesome. It's like you write a page, but then that page is kinda like a template for all other pages. It's SUPER COOL! You can even do stuff like put, say, a hyperlink on that page-- AND EVERY OTHER PAGE WILL AUTOMATICALLY GET THAT HYPERLINK!
So, like, some coder back in 2008 did just that, right? Put a few hyperlinks. Cool cool cool.
But then oh shit bummer-- a page in the website that uses the masterpage-- and I mean, this is serious code red all hands on deck problems yo-- that page is in a subfolder. Right, so it's like \SubFolder\OhNo.aspx!
NOW NONE OF THE HYPERLINKS WORK! Because the hyperlink is all "Hey, I'm a hyperlink to CoolPageOne.aspx", and it's l'il buddy is also just fucking around going "I'm a hyperlink to CoolPageTwo.aspx".
BUT THERE IS NO \SubFolder\CoolPageOne.aspx.
None. None. None!
NONE!
But me, Imma looking at the codes, and I can see it. I can see the solution that was graced from upon high unto us mortals. You are going to totally shits all yourselves with the brilliance! I mean, you can probably see it from where you sit and think and eat. Right, you can see it?
What do you do when you have hyperlinks in a single, central location that break like alls I just described right up a scrolls or two? The answer should be ABSOLUTELY obvious.
I'd use spoiler tags to hide the brilliance until you worked it out yourselves (you wouldn't hahaha it's okay). Whatcha be doing is this: You go around and identify ALL the pages that get mistargetted. I'll call them like I did before CoolPageOne.aspx, CoolPageTwo.aspx-- and so on (it's cannon because I used the same name). Okay, you find all of those pages--
AND YOU COPY THEM INTO \SubFolder!
Fixed. Fixed, motherfucker yes, fixed! The hyperlinks Just. Fucking. Work!
HAHAHAHAHAHAHAHAHAHAAHAH!!11!!MONDAY!AND!ALREADY!THIS!SHIT!!!!twelve
This might help you:
http://www.west-wind.com/weblog/posts/2009/Dec/21/Making-Sense-of-ASPNET-Paths
-
@morbiuswilters said:
@Ben L. said:
You mean this discussion was pre-generated by Community Server's developers and shipped with every installation of CS and just disabled in the settings?
The really eerie thing is they knew you were going to say that and hard-coded it into the aspx many years ago.
Telligent® Community™, use it today!
-
