justmattb

No change in archive name:

Archive name: db_%Y-%m-%d_%H-%i-%s
Example file in “Backups”: db_2013-03-26_04-05-20.tar.gz

Noticed the following:
Folder shows: ftp://ftp.mysite.org:21./
*Wonder if that “.” at the end is affecting something

Size:
All show “?”

Time:
All show “January 1, 1970 at 12:59 am)

Same for FTP

Today I observed that multiple daily backups have been created, yesterday five, and today seven bacups have been written. The timestamps were scattered unregularily across the respective mornings. All had status O.K., since the limit of 20 was not yet reached on that directory and consequently, no deletion attempt did occur. It will probably, when the directory reaches the 20 entries.

I had noticed the same thing. Seems like something messed up with how this uses cron.

I am having the same issue. To add one another piece, if I go in and try to manually delete them through “BackWPup Manage Backup Archives” it also gives me an error that is not able to delete them, but removes the one I tried to delete from the listing (even though it is correct that it didn’t actually delete anything)

Yeah, that part doesn’t work for some reason. But the part that I wanted to use from it was the “Link Roundups”. So I capture some links during the week, then at the end of the week, this allows me to very easily post those in a roll-up post. Again, thanks!

Okay, so I did need the change you sent me earlier:

RewriteCond %{REQUEST_URI} (argo-this\.php|timthumb\.php|phpthumb\.php|thumb\.php|thumbs\.php) [NC]

But after that, it looks like it was a mod_sec rule in place in my hosting environment (HostGator) that was preventing me from capturing URLs outside of my own domain. Now that they’ve fixed that for me, this is finally working. Thanks again!

Looks like it might be a hosting environment thing. Just did vanilla install of the Argo Links plugin over at HostGator and cannot add a link from an external site (404 error). Will have to check with them.

Yeah (MAMP). Still scratching my head with the site I am actually trying to use this on, but hoping I’ll figure it out. At least I know it does work.

No worries; thank you! I went ahead and tested locally from 3.3.1 up to 3.5.1 and with vanilla installs, everything seemed okay. Wondering if it is something else going on. Maybe theme… Maybe hosting environment… Just don’t know.

With the local install (3.5.1), when I added BPS, I initially got the same error message, but just adding argo-this\.php to RewriteCond %{REQUEST_URI} piece fixed it. Doing that allowed me to add URLs from my site and from other sites. Really, really strange behavior right now that I can’t seem to pin down.

Guess I should have looked at the issues page:
https://github.com/argoproject/argo-links/issues/6

Looks like others are running into this. The very, very, very odd thing about this is that I did have it working with other sites at some point. Will have to play with this locally and see if I can replicate any of this. Have made so many changes playing around with this today that I can’t tell up from down anymore.

Just sent you a donation for your troubles – and for all the help you’ve given me in the past. Much appreciated.

It is not a premium plugin, you can download it from the Git Repository here:
https://github.com/argoproject/argo-links

That’s okay; I really appreciate the time you’ve given to this!

RewriteCond %{REQUEST_METHOD} ^(TRACE|DELETE|TRACK|DEBUG) [NC]

No change.

This was just the piece that was leftover from the whole BPSQSE section; I did leave everything else intact. Just wanted to make sure I was clear that what you see below is not ALL that was in the .htaccess file.

# BPSQSE BPS QUERY STRING EXPLOITS
# The libwww-perl User Agent is forbidden - Many bad bots use libwww-perl modules, but some good bots use it too.
# Good sites such as W3C use it for their W3C-LinkChecker.
# Add or remove user agents temporarily or permanently from the first User Agent filter below.
# If you want a list of bad bots / User Agents to block then scroll to the end of this file.

RewriteCond %{QUERY_STRING} (sp_executesql) [NC]
RewriteRule ^(.*)$ - [F,L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

Yes it was, but to make sure that wasn’t causing any issues, I simplified it down to just argo-links and reactivated the plugin (and updated that portion of the .htaccess file). The name was just how it came down from Github.