Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Unfortunately must confirm. Use WP 4.53.

    Thread Starter erzlager

    (@erzlager)

    sojweb,

    you made my day :-). Thank you *very* much for your exemplary answer! You taught me something about the function, showed me the corresponding solution out of WP, were very fast and finally did not let me feel any annoyance in case my approach was too dilettantish.

    Great!

    Best regards

    Raimund

    Thread Starter erzlager

    (@erzlager)

    Hello stvwlf,

    thanks for your reply.

    I tried strip_tags but seem to do it wrong :-(. In order to ‘help’ my possible helpers i will explain my problem more in detail.

    First i want to have a post title like:
    <h2><span>Chapter 01: </span>Hello World</h2>

    Then i will style the span-Element with CSS. So far it works fine both in single post view as on the post overview i.e. homepage, archive, search.

    On these overviews the title is a link to the article which has a title attribute within. This shows the span thing like written in my 1. post.

    The original code for this is:

    <a href="<?php the_permalink() ?>" rel="bookmark" title="Link zu »
    <?php the_title(); ?>
    «"><?php the_title(); ?></a>

    I tried strip_tags then in the following way (which works on other places in order to show category description in link titles):
    <?php echo strip_tags(the_title()); ?>

    But that doesn’t work. Either it is not capable to delete tags *within* the_title or the tags are already converted to unicode.

    Maybe with WP it is not possible to handle post titles like this? For an answer i would be very grateful because if it is *not* possible i will have to think for an other way to achieve my goal. I don’t want to have this span stuff around there ;-).

    Many thanks again

    Raimund

    I had the same problem.
    I tested the upgrade to 2.6 on my local WP-install and everything worked like a charm.
    I had used the automatic upgrade for the online install. First step was to delete the files and load them up again via FTP. But that wasn’t enough, i needed to change the file attributes to 744. After that everything worked like wanted.

    Thread Starter erzlager

    (@erzlager)

    Alex,
    i didn’t want to confuse you … It was just a thought i had:
    If i had different CSS-IDs (and/or classes) on album and gallery (view) or another kind of hook i could give instructions with CSS to hide or show an element like the back-button.

    But as i wanted to show the album in a post, not a page (and the galleries on subpages), there is no way to get a CSS-hook; at least i couldn’t think of one.

    At the end i decided to put each gallery into an own post because i could not accept the lack of orientation. May be the hack of tommiehansen is a solution but for this time i made it the other way anyhow.

    You may have a look at this post:
    How to get gallery titles to show?

    Hello,

    as i faced the same problem i found this tutorial fortunately and am very thankful about it.

    I tried it, it works, and i have further (tested and working) suggestions. They all deal with the code snippet to be added under point 5.

    I replaced the depriciated <font>-tag with a semantical senseful <h3> and added the galery description within <p>-Tags plus a <hr /> which is optional of course.

    The fragment in complete is like so:

    if (is_array($picturelist)) {
    $out  = '<h3>Galery: '.$gallerycontent->title.'</h3><p>'.$gallerycontent->galdesc.'</p><hr /><div class="ngg-galleryoverview" id="ngg-gallery-'. $galleryID .'">';

    I would suppose the (X)HTML code inserted is completely up to you; the deciding pieces are the tags included by the dots and therefore the most valuable information.

    Although i estimate this as a great improvement i should mention that i miss the existence of a “back to album”-button because many users will be disorientated by the lack of any information like that.
    But at the moment i don’t have neither enough time nor knowledge to implement this, so it may be good enough for the time being.

    Furthermore a plugin core hack is never a good solution. Hopefully these necessities/possibilities will be included in future versions.

Viewing 7 replies - 1 through 7 (of 7 total)