Forum Replies Created

Viewing 15 replies - 1 through 15 (of 15 total)
  • kellbot

    (@kellbot)

    I’m experiencing this problem as well, and ended up deactivating the carousel module as a temporary work around.

    Thread Starter kellbot

    (@kellbot)

    Thanks, I think I can work with that. At the very least it’s a more viable alternative to just beating my head against my keyboard, which is pretty much where I’m at right now.

    Yeah I think this is just an honest to god bug, I can get it to happen on my testing server too. Unfortunately the original author of AutoChimp isn’t supporting it anymore, but I’ll see if I can come up with a fix.

    Is it the campaign email, or the opt-in email that’s getting sent multiple times?

    If it’s the campaign email you can try disabling the option to immediately send the campaign. That will let you review each email as it goes out. Also make sure ‘ Create a campaign only once.’ is checked.

    Theonion – How many users do you have? I find that if I have more than a few hundred users the sync times out. I’m working on a fix but your best option right now might be to export a list of user email addresses and manually import it into mail chimp.

    quantumvirtual – by default MailChimp sends a confirmation email to people who sign up for your mailing list (including through WordPress). If you don’t want this confirmation sent out you’ll need to check the box that says ‘Bypass the MailChimp double opt-in’

    In order to get the plugin to email posts to your subscribers you’ll need to set up at least a default category mapping on the campaigns tab. Click “Add new post category mapping” and select a template (which you’ll also need to create over on the MailChimp side of things).

    Is this happening when someone new registers, when you manually sync your list, or both?

    After looking at a bunch of other options I decided that Autochimp is still the right tool for my use case, and I’m sad that it’s fallen out of development.

    It actually is still working for my needs (sync a small list of users to mailchimp and notify them when new posts go up) but could definitely use some love. I extended it to limit signups to specific user roles (something I needed) and I’m going to spend some time with it and see if I can duplicate / resolve some of the issues other folks are having.

    I’m working on setting up php unit tests for autochimp, if anyone is interested it’s up on github (not that there’s much to see yet): https://github.com/offbeat-empire/autochimp

    I’ve been following this thread with great interest. This plugin is the only one that has provided a rational solution to the onslaught of spammer registrations we get. Unfortunately we’ve been getting a ton of “Spoofed IP” false positives lately, and the captcha page doesn’t play nice with one of our plugins (CiviCRM specifcally).

    I had to disable the plugin as a workaround, and I’m super bummed because until now it has been a lifesaver for us. I know you’re stopping development on this in favor of other projects, but the option to disable the “Spoofed IP” check would be a much appreciated work around until we can find another solution.

    Thread Starter kellbot

    (@kellbot)

    I managed to add filters for my custom post types with a few tweaks to the plugin code.
    The basic process, for anyone who wants to do it on their own:

    Modify sphinx.conf to include a new attribute, isForum (or whatever post type) and edit all four sql statements to query this post type.

    Edit /wordpress-sphinx-plugin/php/sphinxsearch_frontend.php and mimic the structures used for comment/post/page/tag filtering. There are a handful of places this needs to be done.

    Edit the widget/panel template files to include the appropriate checkboxes.

    Obviously these changes will be lost on update, so right now I’ll have to hand-merge updates. I’m going to try to write a few hooks that would make this a more generic process for others, if you’re accepting mods to the plugin.

    Thread Starter kellbot

    (@kellbot)

    I managed to filter out the stuff I didn’t want by adding a link to the sphinx config explicitly including only the ones I did.

    p.post_status = 'publish' \
            group by p.ID

    becomes

    p.post_status = 'publish' and \
    	p.post_type IN ('post', 'topic', 'reply', 'page') \
            group by p.ID

    Since I don’t see any filters / hooks in the plugin I guess I’ll have to fork it to support selectors for custom post types.

    Thread Starter kellbot

    (@kellbot)

    Thanks for the quick response. To clarify: the filters don’t appear to be applied to the rest of the_content if I use the shortcode. The shortcode looks great. What’s really weird is that the rest of the content isn’t getting its curly quotes filtered out. I did a ton of testing, and the only difference between posts which appear correct (straight quotes) and incorrect (curly quotes) is the presence of my shortcode. If I comment out the call to yarpp_related() in the shortcode, quotes are once again straight as intended.

    The filter we’re using to remove curly quotes is Unfancy Quote. It’s dead simple.

    I know this is an off-label use, but I’m totally baffled by this behavior.

    I figured out why this is happening:

    We’ve been using Post Expirator for a long time. We used to expire our posts a year from creation, but then switched to expiring all of them at the end of the month.

    It looks like at some point, the arguments stored in wp cron changed from being stored as a string to an integer. So the post ID argument went from being “1776” to just 1776. WordPress apparently considers these two different values, and as a result wasn’t deleting the old cron item when we updated our expiration dates.

    It would be great if the plugin could be updated to double check for the older style entries when updating, just so those get cleared too. Meanwhile I’m hand cleaning the cron tasks of errant items.

    Some more background on this problem: looking at the Cron schedule there are two expiration events: one set for a year after the publication date, and also the correct one. We don’t have any default date set in the Post Expirator settings.

    The edit post page shows the correct date.
    If I update or change the expiration date, the date which was correct before will change, but the first incorrect date still persists. It’s like it isn’t clearing all of them out or something.

    You can make an event span multiple days (long events), but so far I’ve not seen a way to make a single event have multiple non-consecutive days.

    It’s functionality I’m interested in myself, so I might take a stab at writing an add-on to do so if it’s not a feature that’s already supported.

    Thread Starter kellbot

    (@kellbot)

    Thanks!

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