Recent Topics

[6.9.3] observations/questions re URL & tiny URL & Dev-Menue

Started by on Jun 07, 2018 – Contents updated: Apr 24, 2019

Jun 07, 2018 13:03    

We run a 6.9.3 version (which has gone through several upgrades) in Multi-Domain Setup and observe some behaviour that - for perfect performance - needs a fix, which probably result from a shacky basic configuration.

our .htaccess is identical to sample.htaccess

For general understanding: should in a healthy setup work ALL options for 'Collection base URL' and/or 'Tag page URLs' (as well as all the other setup-options) given in the backend 'Collection base URL' or is it normal that some would not function?

There is an observation regarding the Dev-Menue: for all collections we see there 'Collection = "name"' and 'NO INDEX', which is not really helpful.

And finally: Tiny URLs are not working in all collections.

What would be the conclusion of this three observations (if they are related)?

And a remark: it would be helpful having somewhere documented how Tiny URLs are generated or if they are stored permanently, where one would find them in the database ..

Apr 20, 2019 01:01

Some stuff really takes time. I want revive this old case as i never have followed up on it nor solved the problem. And now we happen to experience the situation again in a new installation. While above mentioned version was 6.9.3., now it is 6.11.0

@fplanque: .htaccess should be working, otherwise b2e would probably not work at all. b2e installation delivers already a lot ...

As a starter, maybe I repeat the first question from above:

For general understanding: should in a healthy setup work ALL options for 'Collection base URL' and/or 'Tag page URLs' (as well as all the other setup-options) given in the backend 'Collection base URL' or is it normal that some options would not function? Talking for example about

Collection base URL:

In our case, some of this given choices are not working and I just need to know, if it is a mistake in the setup or if make 'all' options work, needs additional tuning anyways.

Probably related to this question are tiny url. As example, doesn't show, what it should.

The same with help-link ... whilst works well

How can i fix this?

A big thanks already for reading it!

Apr 20, 2019 01:54


The following frequent issues seem to apply to your post: (This is a semi-automated response):

  • You did not provide a screenshot (as requested for support)
  • You did not provide the Name / URL of your webhost (as requested for support)


If I say I don't understand the question and you repeat exactly the same without trying to rephrase, I still don't understand.

From what I halfway understand, my answer would be: yes all options should work unless you have a server config that prevents it (ignored .htaccess for example)

Please isolate ONE problem and give me the following info:

  • What URL is not working?
  • What do you get?
  • What did you expect?
  • Screenshots

Apr 22, 2019 09:37

hi @ramadama

Regarding your last post #5 I have had some tiny url's not working and will try to find the info on that but note

doesn't work: ( this is subdomain-setup)
is not a subdomain of
can only be a subdomain of

maybe you mean a parked domain or a redirect etc.

Apr 22, 2019 10:55

sorry, i picked the wrong example ( in screenshot it is the right one), the last line of my post should read:

doesn't work: ( this is subdomain-setup)

Another observation, which i hope is more helpful than distracting:
There is a difference in performance depending on how 'Single post URLs' is set
Use param: post ID E-g: is showing the content while
Use extra-path: post title E-g: is not working


It seems that 'connecting' ( in German it is: Webspace verbinden - Domain mit Website bzw. Ordner auf ihrem Webspace verbinden) Webspace as 1und1 is doing it, is not doing the job as b2e would require it. We don't understand what causes the broken links nor how to find out what is missing ..

Apr 23, 2019 13:37

I see the same problem on the screenshots of both sites. Any URL that uses extrapath info is not passed to b2evolution and lands a-on a 1&1 error page.

This is due to the fact that the 1&1 webserver is NOT executing your .htaccess file. You need to ask 1&1 why.

Apr 23, 2019 16:40

there was only a tiny detail required: it needed uncommenting the line

# RewriteBase /

in .htaccess

This post has 1 feedback awaiting moderation...

Form is loading...

Photo gallery software – This forum is powered by b2evolution CMS, a complete engine for your website.