amityweb
Forum Replies Created
-
I think each translated page is a post in the database
So WooCommerce make a change and say other plugins need to be disabled or updated? I can see its Advanced Custom Fields is causing the issue, which is a necessary plugin for the site to work.
Forum: Fixing WordPress
In reply to: Making payments with Stripesorry have removed my post I changed my mind, but cant delete it. I changed my mind about posting because we have several servers and the server in question IS upgradeable. I thought it was on another server we have which we cannot upgrade PHP on because they are Centos 6 with 32bit. Using Virtualmin/Webmin. Yes we should upgrade them but its a massive task when you have so many websites on them. You cant have these latest versions of PHP on Centos 6 32bit apparently.
There was no warning on the upgrade. There should be an option to NOT upgrade, OR you have a different plugin released for such a major change. We choose to keep the old servers, so we should not have had the upgrade.
Luckily after I posted I realised I was on a different server, so its not so serious I can upgrade, but if it were on the server we cant upgrade on then it would be a serious issue. I know now we must NEVER upgrade the Stripe plugin on any site on that server else it will break and then we’re screwed.
Forum: Fixing WordPress
In reply to: Making payments with StripeI believe some old servers cant be upgraded, so anyone on such a server is screwed if they upgrade. There was no warning for me when I upgraded. Luckily I can upgrade the server I just upgraded the plugins on, but I have another server which is Centos 6 32 bit which just cant have PHP 5.6+ on it I dont think. No repository for it.
So there should be a block to upgrading the plugins unless PHP 5.6 is installed. Especially as we use Jetpack to upgrade plugins. If the plugins are updated on sites on that old server, they will break. Its a massive task to switch all sites to a new server.
Ah I solved my issue:
https://gist.github.com/ianhampton/eee8f8ea1a6280db8bbae3944c07a451The only issue with this is its an inline attachment in the body, so my mail client is not showing there are any attachments in it. Hope this is not a problem for any email clients.
So we dont need to copy a temp file now as we dont need to use add_uploaded_file()
// Get attachment path $attachment = get_attached_file($posted_data['attachment-id']); // do some replacements in the cf7 email body $mail = $wpcf7->prop('mail'); $mail['attachments'] = $attachment; $wpcf7->set_properties(array( "mail" => $mail ));This works fine for you?
$submission->add_uploaded_file('pdf', '/path_to_my_file.pdf');I cant get any attachments to add to my email.
About the deletion, I used this to copy it to a tmp folder. The tmp folder is also deleted hence the mkdir!
// get attachment from attachment-id in form $attachment = get_attached_file($posted_data['attachment-id']); $attachment_filename = basename($attachment); // Create a temp copy of the file $upload_dir = wp_upload_dir(); $temp_file = $upload_dir['basedir'].'/tmp/'.$attachment_filename; // Copy file to temp location (because Contact Form 7 deletes it later!) mkdir($upload_dir['basedir'].'/tmp/'); copy($attachment,$temp_file); // Attach to email $submission->add_uploaded_file('pdf', $temp_file);My problem is its not attached to the email
So I notice your code for 1.61 has the fix. But ours states 1.61 and it has the line:
$method = wp_parse_args(substr($nested_query_url, stripos($nested_query_url, ‘?’) + 1))[‘method’];So very strange??
oh have you? I didnt realise. Its not showing in our wordpress updates yet. We have version Version 1.61, and this had the error in it. But if its fixed we can just wait for the next update and hopefully it will keep working.
My meaning is that plugins should not be released with new PHP code that wont work on old PHP, else many websites will just break. I mean if you really must update your code for only newer PHP then release a completely new plugin so sites using the old one wont break, or add a check to run both code depending on the version. but I guess it was just a mistake and not intentional.
- This reply was modified 9 years, 4 months ago by amityweb.
Making that change fixes it but have to block this plugin from updates now. You need backward compatibility OR a new plugin to be used on new PHP, not just upgrade a plugin for new PHP that is used on older PHP versions.
You talk about PHP versions, but it worked before so are you saying the update added code only newer PHP could handle so breaking all sites with this plugin on older PHP versions? We cannot upgrade PHP on the server, as the server is old, you cant just upgrade PHP, its a big job.
Yes mine stopped doing it. First time it happened I deleted all backups and looked at settings. It didn’t happen again until several days later then just created 30Gb of files in no time at all and brought the server down again. I have disabled backups and also made the directory unwriteable so it cant create backups now.
The site has been REALLLY slow for days, and its so much faster now. i think ithemes backups must have jsut been constantly running for some reason and slowing it down.
So I think they were actually enabled. I have disabled them. I thought they were disabled because if I went into the settings there was nothing to indicate it was enabled. The schedule setting was off for example. So I have no idea why it was doing it several times a minute.
I am also getting a few emails every minute saying the backups are attached (although they are not).