Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • I know only half the answer, and I want to do the same thing as you (replace the default content that is…).

    When you hover over the theme selection in the sidebar at the right side, you see the delete and the checkmark icon? Click the checkmark, that will define this theme as default for your next newsletters.

    That’s one less thing to do at least

    Thread Starter flammanj

    (@flammanj)

    I’ve already contacted you, but this is for other people who might have the same needs as me.

    In quick-event-manager.php I found the lines where the string output is built.

    I changed line 550 from
    $bottom = $year
    to
    $bottom = '<span class="year">'.$year.'</span>';
    and now I have the year wrapped. It would be possible to wrap the day and month too this way.

    Next, on line 411 there is
    $content .= '<a href="' . get_permalink() . '"'.$target.'>' . $post->post_title .$titlecat . '</a>';

    here I added class=”title”, which gives the title link a class named “title”.

    There are lots of other places within the file where you could change the strings, but it takes some patience to find the exact place that fits your configuration.

    Thread Starter flammanj

    (@flammanj)

    Update:I could resolve some of the issues. I had to go through the configuration pages of QEM in the admin dashboard and save every configuration, even without changing anything. This saved default values to where they belong and the undefined index errors disappeared form the dashboard.

    The messages in the event editor (when creating new events) and on the front page remain. At the end of the debug message on the frontend, the events items still get output and are accessible.

    This means, when ignoring the debug output (set debug to false in the wp-config.php), the event plugin is now working. I would still like to know if the debug messages are intended behaviour or if there is a way to make them disappear altogether, even in debug mode .

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