Home›Support›English Support›[Resolved] Warning: ftp_fget() expects parameter 1 to be resource, null given
[Resolved] Warning: ftp_fget() expects parameter 1 to be resource, null given
This thread is resolved. Here is a description of the problem and solution.
Problem:
I just purchased WPML and I get the following error only when the 'WPML String Translation' plugin is activated.
Warning: ftp_fget() expects parameter 1 to be resource, null given in /wp-admin/includes/class-wp-filesystem-ftpext.php on line 146
Warning: ftp_mkdir() expects parameter 1 to be resource, null given in /wp-admin/includes/class-wp-filesystem-ftpext.php on line 560
When I deactivate the 'WPML String Translation' plugin the error goes away.
This error will occur on the published website and also when I edit a webpage within WordPress. Any ideas what is causing this? I literally just installed WPML and I'm using the Avada WordPress theme which is said to be 100% compatible.
**EDIT**
I resolved the first error by increasing the Memory Limit to 256M. I am still getting the second error:
Warning: ftp_mkdir() expects parameter 1 to be resource, null given in /wp-admin/includes/class-wp-filesystem-ftpext.php on line 560
Solution:
I found the solution to the issue. The owner of the core wordpress files was set to my personal user. I changed this permission to be apache and everything seems to be working.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
I just purchased WPML and I get the following error only when the 'WPML String Translation' plugin is activated.
Warning: ftp_fget() expects parameter 1 to be resource, null given in /wp-admin/includes/class-wp-filesystem-ftpext.php on line 146
Warning: ftp_mkdir() expects parameter 1 to be resource, null given in /wp-admin/includes/class-wp-filesystem-ftpext.php on line 560
When I deactivate the 'WPML String Translation' plugin the error goes away.
This error will occur on the published website and also when I edit a webpage within WordPress. Any ideas what is causing this? I literally just installed WPML and I'm using the Avada WordPress theme which is said to be 100% compatible.
**EDIT**
I resolved the first error by increasing the Memory Limit to 256M. I am still getting the second error:
Warning: ftp_mkdir() expects parameter 1 to be resource, null given in /wp-admin/includes/class-wp-filesystem-ftpext.php on line 560
If the issue does not occur when running the site with WPML plugins only, please reactivate the other plugins one by one while investigating when the problem occurs again.
Please also change to one default theme (Twenty Twenty-one, for example) and check if the issue persists.
Thank you for the reply. I already had all other plugins disabled, with the exception of Avada Core and Avada Builder. Avada theme says it is 100% compatible with WPML.
I tried switching to the 2021 theme and I am not receiving any errors when WPML is active.
When disabling all WPML plugins, my Avada theme is working perfectly fine, but the moment I enable it I get several errors on back-end of website and also on front-end.
It almost seems like Avada isn't 100% compatible. I am using Avada v7.2.1, which is the newest version available. Maybe it's an issue with Avada?
Attached is a new image of the errors I receive when editing a page from within WordPress. This is with the Avada theme active and only the WPML plugins active (along with Avada Core and Builder).
Please let me know if there is anything I can do to resolve, otherwise I'm gonna have to scrap this plugin and give Polylang a try.
Thank you for the quick reply. I followed the steps to migrate the site to Cloudways be get the following message: "We are unable to contact the source site. Due to this the migration cannot be completed."
I tried 3 different times and double-checked the authentication.
I did not try this originally. I tried just now using http:// and https:// and neither works. Any other ideas? Are you able to contact the source site on your end?
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Since the migration process failed, I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Our Debugging Procedures
I will be checking various settings in the backend to see if the issue can be resolved. Although I won't be making changes that affect the live site, it is still good practice to backup the site before providing us access. In the event that we do need to debug the site further, I will duplicate the site and work in a separate, local development environment to avoid affecting the live site.
- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: hidden link
Please, let me know if you need any additional details. Thank you.
I definitely appreciate the quick responses. The website I am working on is our internal testing website that is hosted on a local server. I'm not sure how I can provide you public access. Unless you want to take the time for a public screen share to troubleshoot the issue?
If you come across problems while creating it, please feel free to ignore(exclude from the backup) both uploads and cache folders.
I'm enabling the proper field for your to share this copy, you'll see it in your next response.
Alternatively, you may use any file sharing service that you prefer and share the link in the ticket(your next response is being marked as private, only you and I have access to it).
I found the solution to the issue. The owner of the core wordpress files was set to my personal user. I changed this permission to be apache and everything seems to be working.
