amsross
Forum Replies Created
-
Ok, I’ve done some additional debugging and trial-and-error now that the issue has been narrowed down to being ACF-related.
After reviewing the custom fields that have been attributed to
eventandevent-recurringI noticed a field calledevent_idwhich I figured might be a reserved name.Bingo! I namespaced it and everything is working as expected.
Thankyou for your responses to my issue!
It appears the issue is caused when custom fields are being used on Recurring Events (through Advanced Custom Fields, here). If I enable them on
event, everything works as expected, but when I enabled them foreventandevent-recurring, the duplication issue arises.I have tried toggle “Enable Custom Fields” in the Events Manager Settings but this didn’t change anything.
I’m using WP v3.9.1 with a standard install (no multi-site, etc). The theme I’m using is based on roots (https://github.com/roots/roots).
I’m hooking into the following filters in my theme:
em_accepted_searches,em_event_output_placeholder,em_events_build_sql_conditions,em_events_get,em_events_get_default_search.
All of the filter functions require thatis_admin()be false before executing, so I can’t imagine how they would affect the actual creating/updating of events. Additionally, I’ve tried removing all of my customfunctions.phpcode and still encounter this issue.I’m currently using v5.5.3.1.
Here is a demo/example of what happens when I create and then edit the content of a recurring event: http://imageshack.com/i/f0155wgZg
Deleting the recurring event does not delete the spawned events.
The events have custom fields associated with them.
Forum: Plugins
In reply to: [Email Subscription] On the footer?I know this is old, but this could be useful to others who may be wondering.
You could widgetize your theme: http://codex.wordpress.org/Widgetizing_Themes
Or you could put something like this in your theme:
<?php $EmailSubscriptionWidget_options = array( 'title' => 'Subscribe to my posts', 'success_msg'=>'Thank you for subscribing', 'fail_msg' => 'Some unexpected error occurred', 'submit_button'=>'Subscribe', ); the_widget('EmailSubscriptionWidget', $EmailSubscriptionWidget_options); ?>And that is how post necromancy is done!
Thread necromancy!
I ran into a similar issue and I think it was stemming from a missing
</object>tag in the embed. You can fix this yourself around line 135 of the php file/wp-content/plugins/degradable-html5-audio-and-video/degradable-html5-audio-and-video.phpby changing$output .= $fallbackpl.'</div>';to read$output .= $fallbackpl.'</object></div>';In case it is of any worth to anyone I edited ianhirschfeld’s code (above) to work with a permlink structure of /%year%/%category%/%post_name%/%post_id%/ :
function remove_page_from_query_string($query_string) { if ($query_string['name'] == 'page' && isset($query_string['year'])) { $post_year = $query_string['year']; $page_index = $query_string['p']; $page_num = $query_string['p']; $cat_name = $query_string['category_name']; list($delim, $page_index) = split('/', $query_string['page']); $query_string = array(); $query_string['year'] = $post_year; $query_string['category_name'] = $cat_name; $query_string['paged'] = $page_num; } return $query_string; } add_filter('request', 'remove_page_from_query_string');Obviously this is nothing that ianhirschfeld’s example didn’t cover, but something for comparison for PHP-unfamiliar users out there.