Mike

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 49 total)
  • Author
    Posts
  • Mike
    Participant

    I still need to know if this is going to cause caching issues:

    As for the caching question, my question is specific to the monthly view. If we are showing the available # of tickets and the monthly view and caching the page, will it show accurate seat numbers?

    Mike
    Participant

    This is still a critical need for any power user of TEC Pro, and manually culling the database of event specific featured images is a major hassle. For the community, I think there needs to be some sort of option for admins to accomplish this with relative ease.

    Mike
    Participant

    I was able to take care of this myself. By removing the featured images from the database, I was able to shave 800 Megs off of the database size.

    However, I would still like a SQL snippet from Modern Tribe to accomplish this for future maintenance cycles, as it was quite laborious to do so manually.

    Mike
    Participant

    Here is a starting point from a plugin perspective that delete’s ALL featured images. It would obviously need to be modified to only delete expired events.

    https://wordpress.stackexchange.com/questions/43320/query-to-delete-all-featured-images-and-remove-post-meta

    I have not tested the above snippet at all.

    • This reply was modified 6 years, 2 months ago by Mike.
    Mike
    Participant

    For example, I believe this is the query for the available ticket numbers:

    https://theeventscalendar.com/function/tribe_tickets_get_ticket_stock_message/

    Mike
    Participant

    I’m talking about editing the monthly calendar view, so that it shows the following information in flat view (not in popup)

    Thumbnail Featured image
    Venue
    Event Title
    Available: # (available tickets)
    Single Event Link

    At the very least, can I get the field names of the above fields?

    As for the caching question, my question is specific to the monthly view. If we are showing the available # of tickets and the monthly view and caching the page, will it show accurate seat numbers?

    Mike
    Participant

    I should clarify, the tickets are imported, but are not carried over properly. See attached screenshots for an example.

    This puts all of the tickets as “sold out”, even if they technically have inventory remaining. I am guessing this has something to do with Global Inventory for the event not being set during the upgrade process.

    So my question is, what do I need to do for tickets to be accessible, or to convert properly during the upgrade?

    Thanks!

    Mike
    Participant

    Something about this seems off. The Filter Bar, and in fact all of the “add on” plugins”, do load their own stylesheets. For example:

    Event Tickets Plus has the following sheets in wp-content/plugins/event-tickets-plus/src/resources/css
    admin.css
    meta.css
    tickets.css
    wootickets.css

    Filter Bar has the following sheets in wp-content/plugins/the-events-calendar-filterbar/src/resources/css
    filter-admin.css
    filter-view.css
    filter-view-mobile.css

    According to your response, I should just add my changes using my theme’s custom stylesheet. While this should work, it will result in BOTH the old styles and the new styles being loaded, which is unnecessary extra load and could lead to potential conflicts. I would like to REPLACE the default plugin stylesheets entirely with my own variations, in an upgrade friendly manner. So it seems to me that the proper approach would be to copy over the existing stylesheets from each plugin, make my own alterations, and then upload them somewhere in tribe-events/ as we would do for the primary stylesheets listed in the Themer’s Guide now.

    Are you saying that there is no way to do this right now?

    Mike
    Participant

    Thanks for that info. I did not remember that they were documented in the headers of each file.

    The key issue for the Themer’s Guide is that it doesn’t list the wootickets directory as a potential directory for Event Tickets Plus. In general, I think it should list every potential sub-directory and their respective plugin, at the very least. Ideally, it should have every single modifiable file listed.

    Thanks!

    in reply to: tickets number in photo view #1451290
    Mike
    Participant

    I would be interested in this as well.

    Mike
    Participant

    I should note this is for Woocommerce, if it is relevant.

    in reply to: How to replace CSS files not listed in Themer's Guide #1199644
    Mike
    Participant

    Thanks for checking on how to replace the Ticket plugin CSS, I really need that info for the next phase of our modifications.

    However, I still need to know, how do you replace the mobile stylesheets for TEC and TEC Pro? I know I can additional CSS the custom-events-stylesheets.css or custom-events-pro-stylesheets.css, but I am looking to specifically replace the mobile views of the TEC and TEC Pro stylesheets entirely.

    in reply to: How Adjust the Width of Search Bar Fields #1199640
    Mike
    Participant

    On a related note, what would be the modifications to use the placeholder replace script for the date field?

    in reply to: How Adjust the Width of Search Bar Fields #1199639
    Mike
    Participant

    I can control the width via CSS, but right now it looks at each of the three input fields as the same field. I need to break them down individually, so that I can control their display as a single unit.

    Current layout:
    Existing Layout

    Desired Layout:
    Desired Layout

    So instead of pulling the data via the foreach, I need the queries to pull each individually. I have tried using the existing snippets to rewrite the location and search field placeholders to accomplish this:

    add_filter( 'tribe-events-bar-filters', 'tribe_support_1043886', 1, 1 );
     
    function tribe_support_1043886( $filters ) {
     
        $value = '';
         
        if ( ! empty( $_REQUEST['tribe-bar-search'] ) ) {
            $value = esc_attr( $_REQUEST['tribe-bar-search'] );
        }
     
        $html = sprintf(
            '<input type="text" name="tribe-bar-search" class="tribe-bar-search" id="tribe-bar-search" value="%s" placeholder="%s">',
            esc_attr( $value ),
            'Event Name/Painting'
        );
     
        $filters['tribe-bar-search']['caption'] = 'Label text';
        $filters['tribe-bar-search']['html']    = $html;
     
        return $filters;
    }
    
    add_filter( 'tribe-events-bar-filters', 'tribe_support_1043887' );
      
    function tribe_support_1043887( $filters ) {
      
        $value = '';
          
        if ( ! empty( $_REQUEST['tribe-bar-geoloc'] ) ) {
            $value = esc_attr( $_REQUEST['tribe-bar-geoloc'] );
        }
      
        $html = sprintf(
            '<input type="text" name="tribe-bar-geoloc" class="tribe-bar-geoloc" id="tribe-bar-geoloc" value="%s" placeholder="%s">',
            esc_attr( $value ),
            'Event Location'
        );
      
        $filters['tribe-bar-geoloc']['caption'] = 'Label text';
        $filters['tribe-bar-geoloc']['html']    = $html;
      
        return $filters;
    }

    I added in class=”tribe-bar-search” and class=”tribe-bar-geoloc” to both snippets, and then added in this custom CSS to my child-theme/tribe-events/custom-events-stylesheet.css file:

    #tribe-bar-form input[type='text'] {
    	background: #FFFFFF;
    	border: none;
    	border-bottom: 1px #b9b9b9;
    	border-radius: 3px;
    	box-shadow: none;
    	font-weight: bold;
    	height: 32px;
    	line-height: 1;
    	padding: 5px;
    	width: 50%;
    }
    
    #tribe-bar-form .tribe-bar-search input[type='text'] {
    	background: #FFFFFF;
    	border: none;
    	border-bottom: 1px #b9b9b9;
    	border-radius: 3px;
    	box-shadow: none;
    	font-weight: bold;
    	height: 32px;
    	line-height: 1;
    	padding: 5px;
    	width: 150%;
    }
    
    #tribe-bar-form .tribe-bar-geoloc input[type='text'] {
    	background: #FFFFFF;
    	border: none;
    	border-bottom: 1px #b9b9b9;
    	border-radius: 3px;
    	box-shadow: none;
    	font-weight: bold;
    	height: 32px;
    	line-height: 1;
    	padding: 5px;
    	width: 100%;
    }

    Which SHOULD set the date field to a width of 50%, the search field to a width of 150%, and the location field to a width of 100%. Unfortunately, it is only picking up the width from the #tribe-bar-form input[type=’text’] CSS class, and is setting all three fields to the width listed there (in the above CSS, 50%).

    Any ideas?

    Mike
    Participant

    Is it possible to include this information on the “Checkout” page with Event Tickets Plus + Woocommmerce?

Viewing 15 posts - 1 through 15 (of 49 total)