eflister
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: self pingbacks not workingturns out it was because of the members-access plugin.
if i turn that off, i do get the self-pingbacks.
however, i have to keep approving them, even though i have this set:
“Comment author must have a previously approved comment”why don’t they auto-approve once i’ve approved the first one?
Forum: Localhost Installs
In reply to: self pingbacks not workingturns out it was because of the members-access plugin.
if i turn that off, i do get the self-pingbacks.
however, i have to keep approving them, even though i have this set:
“Comment author must have a previously approved comment”why don’t they auto-approve once i’ve approved the first one?
thanks for the info, i really appreciate it! i upvoted the trac issue. 🙂 current devs: any way you could workaround this? the issue mattyrob linked to includes his small patch that should make it easy. 🙂 i’ve never looked into wordpress guts, but does the current hook for comments moving from unapproved to approved get called for every new comment atm, even if they’re set to automatically be approved? if so, that would be adequate for the purposes described here, wouldn’t it?
afaict that plugin requires individually signing up for each post — i want something more like subscribe2 that allows you to sign up for the whole blog at once (or by category/tag filters). why not add this to subscribe2? is there a plugin that already does it? i can’t find one…
kat got back to me – she says inline images aren’t expected to work. she’s updating the plugin for wp4, but not with any timeline since it’s just volunteer. she mentioned postie as an alternative — i’ve tried it and it works for inline images and attachments fine. wp plugin search doesn’t bring up postie when you search for ‘post by email’ — ugh so lame.
postie works and also uses the blog/wp-content/uploads approach.
i found this, where you discuss relative merits vs jetpack and postie.
http://wptavern.com/wordpress-3-7-to-remove-post-by-email-feature-in-favor-of-official-pluginif i read correctly, the one thing this does that those don’t is import the old “wordpress/settings/writing” values? and even that didn’t work for me until changing one of them?
Forum: Plugins
In reply to: [BackWPup – WordPress Backup & Restore Plugin] logs not deletingok, i mailed you.
for the public record:
now it looks like my logs have been working correctly since feb 21, i
must not have gotten the upgrade earlier than that, even though i
thought i had. thanks for the fix!i sent screenshots showing the pagination issue of the backups that
i mentioned. all 31 pages have all 612 items, even though it’s
supposed to be paginating every 20. (minor issue — i actually prefer
having them all on one page).-e
Forum: Plugins
In reply to: [BackWPup – WordPress Backup & Restore Plugin] logs not deletingi upgraded a couple times since you said it was fixed (now at 3.1.1) and the behavior is exactly the same. i no longer see a caption that says oldest logs will be deleted first, did you “fix” this by just deleting that caption? or do i need to manually delete my 49 old logs before the fix will work?
also, just noticed that on the “backups” page, i have 606 items. i like everything to be on one page, so that’s fine with me. but it says there are 31 pages of items — each page shows all 606. under “screen options” it is set to show only 20 at a time, seems to be confused…
Forum: Plugins
In reply to: [BackWPup – WordPress Backup & Restore Plugin] logs not deletinghere’s one of the old logs:
2013/03/05 03:14.48: [INFO]: BackWPup version 2.1.17; WordPress version 3.5.1; Copyright © 2013 Inpsyde GmbH Author: Daniel Hüsken 2013/03/05 03:14.48: [INFO]: BackWPup comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. 2013/03/05 03:14.48: [INFO]: BackWPup job: 1. daily auto 3am; DB+FILE 2013/03/05 03:14.48: [INFO]: BackWPup cron: 0 3 * * *; Wed, 6 Mar 2013 @ 03:00 2013/03/05 03:14.48: [INFO]: BackWPup job started by cron 2013/03/05 03:14.48: [INFO]: PHP ver.: 5.3.8; apache2handler; WINNT 2013/03/05 03:14.48: [INFO]: MySQL ver.: 5.5.28 2013/03/05 03:14.48: [INFO]: curl ver.: 7.21.7; OpenSSL/0.9.8r 2013/03/05 03:14.48: [INFO]: Temp folder is: C:/[...] 2013/03/05 03:14.48: [INFO]: Backup file is: C:/[...] 2013/03/05 03:14.48: 1. try for database dump... 2013/03/05 03:14.48: Dump database table "wp_commentmeta" 2013/03/05 03:14.48: Dump database table "wp_comments" 2013/03/05 03:14.48: Dump database table "wp_jp_advancedrss_cache" 2013/03/05 03:14.48: Dump database table "wp_jp_advancedrss_templates" 2013/03/05 03:14.48: Dump database table "wp_links" 2013/03/05 03:14.48: Dump database table "wp_options" 2013/03/05 03:14.49: Dump database table "wp_postmeta" 2013/03/05 03:14.49: Dump database table "wp_posts" 2013/03/05 03:14.49: Dump database table "wp_subscribe2" 2013/03/05 03:14.49: Dump database table "wp_term_relationships" 2013/03/05 03:14.49: Dump database table "wp_term_taxonomy" 2013/03/05 03:14.49: Dump database table "wp_terms" 2013/03/05 03:14.49: Dump database table "wp_uam_accessgroup_to_object" 2013/03/05 03:14.49: Dump database table "wp_uam_accessgroups" 2013/03/05 03:14.49: Dump database table "wp_usermeta" 2013/03/05 03:14.49: Dump database table "wp_users" 2013/03/05 03:14.49: Database dump done! 2013/03/05 03:14.49: Add database dump "wordpress.sql" with 3.6 MB to backup file list 2013/03/05 03:14.49: 1. try for make list of files to backup.... 2013/03/05 03:14.54: 2946 files with 96.2 MB to backup 2013/03/05 03:14.54: 1. try to create backup zip (PclZip) archive... 2013/03/05 03:15.27: Backup zip archive create done 2013/03/05 03:15.27: Archive size is 58.48 MB 2013/03/05 03:15.27: One old log deleted 2013/03/05 03:15.27: Job done in 40 sec.[Moderator Note: Please post log files between backticks or use the code button.]
Forum: Plugins
In reply to: [BackWPup – WordPress Backup & Restore Plugin] logs not deletingthat wasn’t my issue — the issue (stated as the thread topic) is that it is not actually deleting the old logs first — it is keeping the oldest and just the single most recent. also, that most recent one is unlike those old ones — it is very short, is classified as “log only,” and contains no detail (as shown). the old ones have lots of detail and were classified as “DB Files.”