Getting /ASSETS_URL_WEB_FULL/home when starting website within browser bar

Permalink 1 user found helpful
I can get to our site using the url/home, and I can migrate the hell out of the site no problems, but when I type in our website into the browser bar I gethttp://url.com/ASSETS_URL_WEB_FULL/home.... I just noticed this after upgrading from a base concrete that was fairly old. Had to do three or four updates to get here, but here isn't all that great if users wont find our site instead getting a page not found. I have the re-write rules in place, so it isn't that. Why would a variable name be inserted into the URL anyway. I could see it if it were the actual value of the variable, but this just throws the url in. Ive searched the forums here, google, the entire concrete site and yet not a single incident of this error. Hard to believe. Thanks in advance for any help provided.

shucke
 
mhawke replied on at Permalink Reply
mhawke
Have a look in your [root]/config/site.php file and comment out any line that defines ASSETS_URL_WEB_FULL

This is an old constant that doesn't appear to be used in more recent versions.
shucke replied on at Permalink Reply
shucke
The variable ASSETS_URL_WEB_FULL is not in site.php, it does have a BASE_URL however. The ASSETS_URL_WEB_FULL does reside in /concrete/config/base.php. Should I comment out the variable in that file?
shucke replied on at Permalink Reply
shucke
Commenting out the variable in base.php does no good. Hasn't anyone else faced this problem? I'm starting to get worried that the site has been down now for over 24 hours with no help on the horizon. Anyone?

Oh, and when I post a reply I get a spinning wheel in black and the dialog looks like it is hung up. Probably not the effect you are looking for on your company website... just sayin...
mhawke replied on at Permalink Reply
mhawke
What version are you on?

Is there a live site we could have a look at?
shucke replied on at Permalink Reply
shucke
shucke replied on at Permalink Reply
shucke
Another issue this upgrade to 5.6.2.1 is having is with blocks. Whenever I try to reference the blocks within the interface for either adding a block to a page or in editing the properties in system and settings, even when trying to look at block types nothing is displayed. I get a blank page. I don't know if that helps shed some light on the problem with the assets bull crap but hopefully someone will recognize what the hell happened to my upgrade and my website. I've spent the last two days trying to get this damn sight running and I don't have time to waste on this. Could someone from concrete 5 weigh in here, or do you just ignore these forums?
shucke replied on at Permalink Reply
shucke
Dear Concrete5

"We think people need to communicate better."

"Things need to work. No software in history has ever been bug free, but you've got a right to expect things to mostly work well. If you're installing some new add-ons on your site, they should do what they said they would, and they certainly shouldn't break your site if it was working before. If you do find bugs, there should be some mechanism to get them addressed."

blah, blah, blah.
shucke replied on at Permalink Reply
shucke
Now I do a restore, fail. Do another restore, and UBER FAIL. What a piece of s!#t.

Now, how do you recover from this crap?

Here is what I get when I try any URL in our website now: ���

Your system of upgrades and restores needs major work. I hate concrete5.
mkly replied on at Permalink Reply
mkly
Hello,
Sorry to here about the frustration you've been feeling trying to upgrade. I'm going to try a few pointers to get you going in the right direction.

I see that you are getting redirected to "ASSETS_URL_WEB_FULL". There is not actually a concrete5 core constant named that. I searched the source for 5.6.1.2 and 5.4.2.2 and did not see that constant defined or used anywhere. It's likely an addition to your site for some custom functionality. If you remembered how and why that was added, it might help get you sorted out. Or if there was a previous developer who assisted in creating the site, you might want to contact them. The reason you are seeing the string is because in PHP if a constant is not defined and the error level is set below a certain point, that constant actually gets turned into a string.

You said this was located in /concrete/config/base.php

https://github.com/concrete5/concrete5/blob/master/web/concrete/conf...

I am not seeing that constant defined there. I wonder if you have some custom modifications going on in the core concrete5 code in your site? Again, this might be something worth contacting the previous developer about.

Let me know what version you are seeing that constant in so we can determine for sure if your core code has been modified and we'll take it from there.

Best Wishes,
Mike
mlocati replied on at Permalink Reply
mlocati
It's a very old constant (used in version 5.4.1).
It has been removed years ago: seehttps://github.com/concrete5/concrete5/commit/3d436f34d8d0ff156f4523...