Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter heinrichplanzer

    (@heinrichplanzer)

    Thanks John, that helped. Wasn’t as difficult as it seemed first.

    Input: /de/home/empfangen4ghr17dkmc

    Settings
    source: ^/de/home/empfangen(.*)
    target: https://example.com/empfangen/?zustellungnr=$1

    Thread Starter heinrichplanzer

    (@heinrichplanzer)

    Hi Mikko. the “nested comments” might have been a wrong interpretation by me, i couldn’t find such occurence now. here’s a 1:1 copy/paste from one of the posts, field post_content. in the second half, after “<!– {” is the yootheme code.
    https://markom-26.planzer.ch/post_content.txt

    Kind regards

    Beat

    Thread Starter heinrichplanzer

    (@heinrichplanzer)

    Mikko, thank you. i can’t tell you how much i appreciate your quick and highly concise answer.

    for the unlikely chance that someone else experiences the same problem:
    i ended up changing utils.php, obviously not perfect, but i’ll block update and make a note in the KB, it’s just one line to add. also used relevanssi_excerpt_content to fix the excerpt. and changed the regex to drop everything after “<!– {“. thats how the segment always starts. otherwise the regex would not work with nested <!– –>.

    function relevanssi_strip_all_tags( $content ) : string {
    	if ( ! is_string( $content ) ) {
    		$content = '';
    	}
            
            
            //custom: avoiding indexing of yootheme builder code
            $content = preg_replace( '/<!-- {.*/ms', '', $content );
            
    	$content = preg_replace( '/<[!a-zA-Z\/][^>].*?>/ms', ' ', $content );
    
    	return $content;
    }
    add_filter( 'relevanssi_excerpt_content', 'pl_fix_relevanssi_excerpt' );
    function pl_fix_relevanssi_excerpt( $content ) {
    
        $content = preg_replace( '/<!-- {.*/ms', '', $content );
        
        return $content;
    }

    relevanssi has the killer-feature of showing and marking the hits when searcing. it’s so much more useful for the visitor, to actually see what has been found.

    you got a new client 😉

    Kind regards
    Beat

    One might ask why metadata is stored in the post content in the first place, when WordPress has custom fields for the specific purpose of storing metadata…

    couldn’t agree more. the theme has it’s origins in joomla and has several non-wordpress-standard implementations. that decision has been made before my time and i’m stuck with it. the theme is not bad otherwise though.

    Thread Starter heinrichplanzer

    (@heinrichplanzer)

    Hi Andy
    thank you very much indeed, that gives some clarification.

    i’m a bit confused how this is even possible. maybe other countries than switzerland do not need to apply taxes to shipping?
    the way it is now, we have to change all shipping costs in order to get “nice prices” when tax is changing. it creates all kinds of problems. do you happen to know if this is will be in a future release? or where could i place such request?

    is there a plugin that solves this?

    Thanks!

    Thread Starter heinrichplanzer

    (@heinrichplanzer)

    Hi Mirko
    yes, this it’s checked:
    https://pasteboard.co/K6GqqNC.png

    and the system is correctly calculating taxes on shipping.

    My problem: i want to enter the shipping prices including taxes. that seems like the normal thing to do, since prices on products are also entered including taxes. i’ve marked it here:
    https://pasteboard.co/K6GtM5j.png

    Thanks!

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