Forum Replies Created

Viewing 15 replies - 1 through 15 (of 56 total)
  • the advice given cubecolour and Rahul is sound. The issues experienced I would say is WP related.

    Why?

    IF you switch from HTML to VISUAL mode after writing in your code, WP automatically changes your code to the shockwave plugin display – thereby breaking it.

    My suggestion?

    Complete your post, and RIGHT before publishing, switch to HTML mode and insert the embed code as directed. Hit “Update” WHILE IN HTML MODE and you should be fine. Do NOT update the post while in VISUAL mode.

    would prefer to wait for a release candidate – but thnx for the consideration

    I can wait – thanks for the quick and warm responses

    Hi Andre – thnx for the quick response on this – for ease going to copy what I had and add the WordPress version:

    Running:
    WP – 3.2.1 – Multisite (folders NOT sub-domains)
    CF7 – 2.4.6 – Network activated
    reCAPTCHA – Huyz edit – Network activated
    CF7 reCAPTCHA extension – 0.0.10 – tried both network and site-based activation, both gave same error re dependencies

    ** this is the setup for a site other than the one listed in my profile by the way **

    doesn’t work for me – i get an error about neither of the dependent plugins being activated.

    Running:
    CF7 – 2.4.6 – Network activated
    reCAPTCHA – Huyz edit – Network activated
    CF7 reCAPTCHA extension – 0.0.10 – tried both network and site-based activation, both gave same error re dependencies

    from other threads 0.9 was released before it was ready and the most current stable version is 0.8.5.2

    if you’re using the calendar widget – try disabling it and see what happens

    +1 here

    hey halcyonblog,

    Are u still having a problem?Visited your site and there’s a calendar thing running and heavily modded (or so it seems)

    IF you’re still having issues:
    1 – what version of the plugin are you using?
    2 – first suggestion is to disable the widget… check if that works. The widget tends to be troublesome in my experience.
    3 – do you see an “events” category?

    hmmm… I dunno what you’d have to do to the guts of the plugin to limit it to 1 month, BUT as they say – there are more than 1 ways to skin a cat.

    The only thing I could suggest is making it seem to the visitor that the calendar only loads for August – only the most nosey/savvy of visitors would notice anything. The edits below try to keep the core functionality of the plugin by making the least possible amount of changes to the code (and clearly commenting those edits that are made), so that should u change your mind you can go back to full displays without a problem.

    Step 1. Use the sidebar widget. It displays upcoming events and links to them, so if you only have events for August, only those events will show.

    Step 2. Edit /wp-content/plugins/the-event-calendar/event-list-widget.class.php on lines 80 and 81:

    Change

    /* Display link to all events */
    echo '<div class="dig-in"><a href="' . $event_url . '">' . __('View All Events', $this->pluginDomain ) . '</a></div>';

    To either this (if using pretty URLs)

    /* Display link to all events */
    /* echo '<div class="dig-in"><a href="' . $event_url . '">' . __('View All Events', $this->pluginDomain ) . '</a></div>'; */
    
    /* My edit to display August only STARTS below */
    echo '<div class="dig-in"><a href="https://[your-domain-here]/category/events/2010-08">' . __('View All Events', $this->pluginDomain ) . '</a></div>';
    /* My edit to display August only ENDS above */

    Or this (if NOT using pretty URLs)

    /* Display link to all events */
    /* echo '<div class="dig-in"><a href="' . $event_url . '">' . __('View All Events', $this->pluginDomain ) . '</a></div>'; */
    
    /* My edit to display August only STARTS below */
    echo '<div class="dig-in"><a href="https://[your-domain-here]/category/events/&eventDisplay=month&eventDate=2010-08">' . __('View All Events', $this->pluginDomain ) . '</a></div>';
    /* My edit to display August only ENDS above */

    Step 3. Remove all calendar based navigation by adding the following to your CSS (/wp-content/themes/events/events.css):

    .tec-month-nav {
    display: none;
    }

    Step 4. If there are ANY links to the “Events” category in your theme – hide them or get of them. If you need to hide these links while displaying other categories – I suggest you look into plugins like SimplyExclude and Advanced Category Excluder

    That should do it.

    Explanation:
    >> Step 1 changes nothing really – just ushers your visitors to using the calendar options you’ve customized

    >> Step 2 hard-codes the “View All Events” link that appears at the bottom of the widget to August of whatever year you set (2010 in the example above)

    >> Step 3 uses CSS to hide the code that allows a visitor to navigate the calendar – forcing them to edit the URI in the browser’s address bar if they want to see anything BUT August of the year you set (meaning you’ll have to adjust the year set in Step 2 at the end of the event every year).

    @alx-xc

    I recommend the following re styling:

    1. Read this CSS tutorial – and use it as a reference

    2. Use attribute selection to differentiate between things (check out Grouping/Nesting in the above link)… eg. If I come across class .someClass on 2 diff pages and want it to look different on each page, I’d most likely look at the <div> tags that the class is applied to OR encapsulated by – usually they are different – allowing you to have “unlimited” versions of the same class…

    – i.e. someClass can be done to display differently in the following case:

    <div id="firstDiv" class="someClass> and <div id="secondDiv" class="someClass">

    In your events.css you’d have:
    #firstDiv .someClass {} – and that would define the styles for the class someClass within any page element with the id firstDiv

    …you’d also have

    #secondDiv .someClass {} – and that would define the styles for the class someClass within any page element with the id secondDiv

    NOTE: when nesting classes, you MAY need to override style definitions in the first occurrence to ensure they are not inherited in the second

    ur still using the your custom template files from 1.5.6 – you’ll find said files in wp-content/themes/[your-theme]/events/

    You need to re-do them with the 1.6 versions (instructions in the Other Notes section of plugin page I believe)

    @ltpromo – these guys have a solution fer ya https://www.ads-software.com/support/topic/403490?replies=5

    @ratreides – could you mark this resolved please – given the answer to the original question was supplied by justinendler here

    @ agilwebdev

    it sounds like all your problems are coming from the widget (sidebar). If this is so and everything else in TEC is working, then read on – if not, then post other errors.

    To fix the link issue:

    – On my own site, I’ve found that is ONLY a problem on the home page. On every other page the widget generates the correct URL. My assumption is that it more likely than not has something to do with how the functions events_get_listview_link(); and events_get_listview_link(); are executed. This creates 2 possible solutions: (a) remove the dependency on the dynamically generated results of these functions (which is the workaround I’m gonna show you); and (b) fix the way these functions work (which I hope the admins will do soon – tbh – given the way TEC is set up a dynamically generated link really isn’t necessary IMO).

    It’s a 2-step process:

    Step 1 – open events-list-widget.class.php in the wp-content/plugins/the-events-calendar folder

    Step 2 – around line 81 you should find:
    echo '<div class="dig-in"><a href="' . $event_url . '">'
    change that to:
    echo '<div class="dig-in"><a href="https://[your-domain-here]/category/events/">'

    To modify the “view all” link (what it says/where it appears):

    To make it appear BEFORE the event list (at the top of it):

    1. cut lines 80 & 81 (with your edit from earlier):

    /* Display link to all events */
    echo '<div class="dig-in"><a href="https://[your-domain-here]/category/events/">' . __('View All Events', $this->pluginDomain ) . '</a></div>';

    2. paste that in at line 63… but be careful – your paste MUST be BEFORE the line that reads /* Display list of events. */ but AFTER the line that reads if( $posts ) { – the money spot is right between those 2

    To make it say something other than “View all events”:
    1. change the same line a la '<div class="dig-in"><a href="https://[your-domain-here]/category/events/">' . __('View All Events', $this->pluginDomain ) . '</a></div>';

    @steve Weblin
    > there is customization for the widget display as well – are you saying you also copied over the events-list-load-display.php file? If so you should be able to customize the look of it.

    > although I agree with you in principle re a smooth upgrade, I also recognize that there is no way for the developers to practically do this – HOWEVER – I think there is the need to put up a notification warning users that custom templates/views from 1.5.6 will not work seamlessly in 1.6 and give instructions (on how) to upgrade said customized templates >> A kind of effect and response that is common in “major” upgrades.

Viewing 15 replies - 1 through 15 (of 56 total)