markomitranic

Hmm, my error. The $args line actually does not separate the “not searched IDs” as it should. i will open a new support topic for that.

Can you please answer the ->ID question here anyway? ??

Well, i guess i should have also added this. This is what i would use it for:
For some reason, i really want the category slug to be forwarded via $_GET to the search code below. The code works if i define the ID myself (for testing purposes), but i need a way to extract the id from the slug that was forwarded ??

$args = array(‘post_type’=> array( ‘pro_artikl’ ), $catID2, ‘posts_per_page’ => -1);

I guess something is wrong with the line
$catID2 = $catID2->term_id;
because it returns nothing when echoed. Normal categories for example return their id with no problems after that line.

And how can we find out a term ID via the term slug? I am not able to do that for some time now. Thanks. ??

$catID2 = get_term_by(‘macola_raid-2’);
$catID2 = $catID2->term_id;

This is what i tried last after hours of searching, and it doesn’t work.

Thanks for your help anyways guys ??

No use, at the moment i am searching for another solution, most probably meaning i will write it from 0. So, the beta website is offline at the moment.

Well for example, if i have a 100%width menu, when you switch to small tablet or lower size, half of the meny items disappear, or in some cases just go beneath each other.

The ease of use guidelines do not allow a “bootstrap standard” hidden drop down menu, nor would it look as it should.

In other words, i dont want responsive scaling, i want a fixed page.
If you take a better look, every seriour website with a lot of information does not use a responsive layout for mobile. they eather fix it, or they make a completely new mobile optimised website. there are reasons for this.

If i want mobile theme, i would install it separately, because the mobile form factor doesnt need all the informations the computer one holds, so the content itself would be diffferent, and formatted diferently and the navigation would be different.

Responsivness for mobile is only an excuse for lazy developers. Responsiveness is made to solve the problem of different resolutions, not the problem of mobile devices ??

Thanks for your response nikeo ??

Shapeshifter, heres the thought process:
-current response features are badly implemented. Why? Because with responsiveness, comes the need to make your content fluid and not fixed. On some websites, like mine, there is a far bigger need for everyone to see the exact same thing.
Response comes with a price for the end user, and that price is that the end user has access to two completely different websites over mobile or over computer, and the end developer has to . This is bad for user experience.
-In my opinion, responsiveness may only work for bloggers and MAYBE forums. In other words, for content that is not of graphical nature or of composition-dependant nature. Or, for people who feel the need to offer completely different experiences depending on the device they are using.
-Bootstraps main feature is not responsiveness, you are wrong there. Its the ease of use for the end developer. It looks nice, saves a lot of time and is pretty much stable. Scripts are flawless most of the time and so on.

So, i really like this theme, and with a little customization it is perfect for my needs, but responsive features are bad for me. ??