[Steven Zahm]

@ bobbyau

The JavaScript console error looks like it is being created by JetPack, not Connections. The error suggests that their is a coding error in the JSON reply causing a line not being ended correctly.

This should be completely unrelated to getting a 403 error when adding an image to a Connections entry. It’s been quite some time since I’ve seen any issues regarding folder/file permissions for images. Try setting the folder permissions for connections-images to 767. Does that help? If it does, my best guess is the web host made a server config change that seems to affect images files being uploaded to the WordPress uploads folder, perhaps whitelisting WordPress as to not break it but will still break when plugins upload images. If that is the case, that would seem odd, cause Connections simply uses the WordPress core functions to upload images, nothing fancy or custom. Don’t build it if it built in, right? :)

It just occurred to me…

The 4.7.1 security update to WordPress is causing users all sorts of trouble with uploading files. This would be the first where I heard images not uploading in Connections. And the first were server 403 errors were being thrown.

Any way, you can read more here:

https://core.trac.wordpress.org/ticket/39550

In this thread the devs are suggesting users install this plugin:

https://wordpress.org/plugins/disable-real-mime-check/

Perhaps give this a plugin a try.

Let me know how things go.

[Steven Zahm]

@ Ryan

Yep it’s odd, but, I assure you, there’s nothing special about Connections or its add-ons when it comes to installation and updating by WordPress. By that I mean, WordPress handles that. I have no custom code there. So, it follows the same process as the many thousands of other WordPress plugins. I’d chalk it up to a glitch in either the install or uninstall functions in WP. My best guess is that file WordPress did not set the correct file permissions when that file was installed making it so it could not be deleted. Seems this does happen and is not unique to Connections.

Any way, glad I could help!

[Steven Zahm]

@ Kate

Here’s a tutorial on how to add custom text fields.

I’d suggest displaying the custom text fields as outlined in the tutorial but, create a custom template override file which contains the display code o you do not lose your work on updates. Here is the link to the tutorial on custom template override files.

Hope that helps!

[Steven Zahm]

yael xu

On the English site, it looks like you are using the SiteShot extension but not on the Chinese site.

Make sure your shortcodes are the same, enabling SiteShot on the Chinese site.

Hope that helps!

[Steven Zahm]

@ yael xu

There is not really an option to set the max width of an image. This is actually set automagically in CSS based on the device’s screen width.

What can be done is use CSS to force a max width to 50px.

Add this to the theme’s custom CSS area:

ul.cn-category-image-container .cn-category-image-block {
    width: 50px !important;
    padding-bottom: 50px!important;
}

That should do the trick. It does make the categories very small and cramped, so tweak as desired.

Hope this helps!

[Steven Zahm]

@ Ryan

That is a WordPress error. It seems for some reason WordPress is unable to delete the existing file so the new version can be installed.

The only way to fix this is to deactivate and delete the existing version and then reinstall the Widget Pack. Since WordPress is unable to do the delete for an upgrade, it might not be able to when you delete the plugin, so, you might have to delete it using FTP.

Hope this helps, let me know.

[Steven Zahm]

@ ken

I’ve read and reread the WordPress Trac ticket about this issue. I’m not certain if this is actually going to be considered a bug which requires fixing.

So…

I just released an update to CSV Import, version 1.4.2, which address the change in WordPress 4.7.1 in a secure way which should now allow you to upload CSV files again.

This update to CSV Import will (err should) work regardless of any changes that may or may not come with WordPress 4.7.2 in regards to this issue.

Hope that helps, apologies for the trouble!

ps. If you installed the Disable Real MIME Check plugin, you should deactivate and delete it.

pss. If you see this same error in the WordPress Media Library when uploading files, then you will still need the Disable Real MIME Check plugin installed. The change I made to CSV Import will not affect other plugins or WordPress when uploading files which throw this error.

[Steven Zahm]

@ yael

I’ve read and reread the WordPress Trac ticket about this issue. I’m not certain if this is actually going to be considered a bug which requires fixing.

So…

I just released an update to CSV Import, version 1.4.2, which address the change in WordPress 4.7.1 in a secure way which should now allow you to upload CSV files again.

This update to CSV Import will (err should) work regardless of any changes that may or may not come with WordPress 4.7.2 in regards to this issue.

Hope that helps, apologies for the trouble!

ps. If you installed the Disable Real MIME Check plugin, you should deactivate and delete it.

pss. If you see this same error in the WordPress Media Library when uploading files, then you will still need the Disable Real MIME Check plugin installed. The change I made to CSV Import will not affect other plugins or WordPress when uploading files which throw this error.

[Steven Zahm]

@ Norbert

I’ve read and reread the WordPress Trac ticket about this issue. I’m not certain if this is actually going to be considered a bug which requires fixing.

So…

I just released an update to CSV Import, version 1.4.2, which address the change in WordPress 4.7.1 in a secure way which should now allow you to upload CSV files again.

This update to CSV Import will (err should) work regardless of any changes that may or may not come with WordPress 4.7.2 in regards to this issue.

Hope that helps, apologies for the trouble!

ps. If you installed the Disable Real MIME Check plugin, you should deactivate and delete it.

pss. If you see this same error in the WordPress Media Library when uploading files, then you will still need the Disable Real MIME Check plugin installed. The change I made to CSV Import will not affect other plugins or WordPress when uploading files which throw this error.

[Steven Zahm]

@ James

I’ve read and reread the WordPress Trac ticket about this issue. I’m not certain if this is actually going to be considered a bug which requires fixing.

So…

I just released an update to CSV Import, version 1.4.2, which address the change in WordPress 4.7.1 in a secure way which should now allow you to upload CSV files again.

This update to CSV Import will (err should) work regardless of any changes that may or may not come with WordPress 4.7.2 in regards to this issue.

Hope that helps, apologies for the trouble!

ps. If you installed the Disable Real MIME Check plugin, you should deactivate and delete it.

pss. If you see this same error in the WordPress Media Library when uploading files, then you will still need the Disable Real MIME Check plugin installed. The change I made to CSV Import will not affect other plugins or WordPress when uploading files which throw this error.

[Author]

Posts