Recent Topics

Subdomain, Bootstrap Glyphicons (and Cookies)

Started by on Apr 30, 2017 – Contents updated: Jun 13, 2017

Apr 30, 2017 22:47    

Using 6.8.8-stable


I set up a new Blog using a subdomain. (Subdomain of Basehost
I switched also Assets-URLs / CDN-Support to URL configured in Basis-Config e.g.

Here is the collection:

I recognized, that bootstrap glyphicons do not work. Also java script comment form does not show up.
What did I miss to configure? Or is this a bug? In this case, is there a workaround?

Thanks in advance, will

In this b2e instance I use three blogs set up usually and one blog setup via subdomain. What I recognized is, although being logged in, after switching to the frontpage of the (subdomain) blog there is no backend line above (sry; don't know the terminus technicus). Is this a common phenomenon?

Baseurl: http//

Subdomain setup: → [webspace content]→ /blogs/

May 04, 2017 20:59

is there anybody who is able and willing to help me solving a problem?
Would be great,
Regards, will

May 07, 2017 21:42


I switched also Assets-URLs / CDN-Support to URL configured in Basis-Config

What if you leave those options as they are configured by default? I mean, keeping the options marked as recommended setting

May 07, 2017 22:04

@mgsolipa there is no skin using recommended setting.. Therefore I've chosen Url in Basic-Config configured.

May 07, 2017 23:47

@saunders can you send a screenshot similar to the one I sent you before?

May 10, 2017 08:17

@saunders the problem is caused by the /blog folder. Try using the full domain ( on the Absolute URL fields.

May 10, 2017 16:09

@mgsolipa Thanks that worked, now Skins an Glyphicons are pretty fine.

But the one problem persists. When I log in from that page. I get this error message shown below. (Only when using this site (subdomain).
If I log in by another Blog I can work in the backend but after switching ot the frontend the login information seems to get lost and I have to log in again.

Maybe it is a cookie problem

May 11, 2017 08:27

And further: like in message form commenting is also not possible. I get the error message seen below.
Actualizing the crump does not work. The error message remains and the message is not delivered.
And there are also problems sending comments.

May 15, 2017 10:56

@mgsolipa here come my collections defaults.

I suppose that the problem roots in baseurl. I set basurl to: To avoid double content I redirect in my host-settings to
The subdomain redirects to
May be it is a cookie problem caused by this.
But I don't know how to handle this in subdomain cases.

I published a post, so you can test it. Try also to login.

Regards, Will

May 19, 2017 11:17

@mgsolipa Maybe there is a bug in the cookie URL by default, The system sets a dot in front of a subdomain. This can't work
I can not correct this by using customized. In this case I get the message: Validation errors: Die angepasste Cookie-Domain muss ein Parent der Sammlungs-Domain sein."

May 27, 2017 22:21

@saunders apologies for the delay, again. I have to admit it's a shame.

Just a comment, I read your tweet, it would be nicer if you send us a bump here before, instead of publishing an angry message in a world-wide social media. We are glad to help you, and we also appreciate if you remember this is free software and free support (there are MANY hours of work that you get in your hand just expecting good will in exchange). Please try to keep that on mind before to get mad.

I tried the comments form at and they work. There is no redirection from to anymore (did you fix it?).

There are no bugs regarding the dot before the cookie domain. The dot means that cookie is used by the domain and its sub-domains. So, if you have, and the cookie domain is set as:, the same cookie will be valid for too.

Another thing that concerned you was the login. You can only set a default collection for login/registration (see screenshot), so all that kind of request will end up going there. I'm afraid there is not so much else we can do in that case. Having: and also working properly under the same b2evolution installation is not possible. There is no way to login at and keep the session in Please read this comment:

If there is something else we can help you with, please let us know. I will put special attention to answer you within a few hours.

May 28, 2017 10:52

@mgsolipa thank you for your support.

You pointed to the fact, that b2evolution software and support are free - and you know I have always appreciated this. You do a great work. If my experience of that awesome CMS would not be that I would have switched away long ago.

To the actual episode: I have tried to keep my ask for support alive by posting new comments, showing my own more or less experimental approaches to solve the challenge by myself. But I'd got no reaction. If you would have posted, that you are busy and within the next two, three weeks you can't deal with it, it would be ok. If you would tell me, that you have no resource to deal with it at all, it would also be ok (but sad). But without any answers it is uneasy. Some (few) of my support tickets ended up void. In secondary concerns I can live with this.

To Twitter. If you (@mgsolipa) or @b2evolution would follow a twitter that contacted you, tweets could be sent as direct messages instead of public ones. It has never been my intention to bully you, but to nudge b2e to see whether my ticket is still on your radar. So please follow my twitter and public attempts to contact you will be obsolete..

Again: I estimate your engagement and b2evolution!

Regards, Will

May 31, 2017 07:19

@saunders thanks for the screeshots, unfortunately I think we are in a dead point. I can't reproduce any of the issues since I have no user account to reset password, nor invitation code to register as a new one.

German is also a handicap, because I can't copy/paste the text in your screenshots into a translator.

Do you mind to send me a backend user with admin privileges? You could send this info in a private message here in Please, consider sending a FTP user as well, so I can look around and see if I'm able to find something "wrong" there.

At this point, I think this is the easier-quicker way to help you.


Jun 13, 2017 01:27

@saunders I changed the cookie domain back to default. The password recovery works well now.

The non-working registration link has nothing to do with your multi-domain setup, it's actually a bug that need to be fixed.

Please, make a general check of your site and let me know anything you find.


Jun 13, 2017 21:08

@mgsolipa Thank you very much for your support! I'll make the general test and let you know if anything needs to be fixed. I'll send PM via the system to you and hope you'll receive it.

This post has 1 feedback awaiting moderation...

Form is loading...

free blog tool – This forum is powered by b2evolution CMS, a complete engine for your website.