wpsnoop: fix Vintage.js plugin conflicts, errors & issues

When the plugin Vintage.js conflicts or throws a PHP error we hope wpsnoop can help you to fix the issue quickly.

Discover which shortcodes wp-options PHP functions database tables and files are created by Vintage.js, plus learn which plugins and/or themes could be in conflict with Vintage.js.

Troubleshooting theme and plugin conflicts is easier when you know what Vintage.js leaves behind after uninstalling it from a WordPress installation, there is a list down below for your convenience.

Expert advice is recommended if you are not technically proficient with PHP, MySQL etc. View support options for Vintage.js

Get professional support for Vintage.js here

When you need professional help with WordPress: get help here

What does Vintage.js version 1.0 add to WordPress? Answers Here.

This is an automatically generated report - it is possible for Vintage.js to perform differently in your installation, previous versions before 1.0 may have created a different set of shortcodes, used different function names or could have created entirely different database tables to store settings and operate. This is not an exhaustive list but shows how version 1.0 of Vintage.js behaves when installed and removed on a clean installation of WordPress.

We have not tested individual shortcodes, features or settings of this plugin but instead have concentrated on the potential for obvious errors and conflicts which can occur, if you need help with the plugin in your local installation you can get WordPress help and support for Vintage.js by clicking here.

Our testing covered the free version of this plugin there may or may not be a paid version or premium version available for purchase that unlocks additional features and could behave in a slightly or very different manner.

Summary of WordPress plugin analysis: Vintage.js

Plugin Slug: vintagejs Internal ID: 77317 Addon Type: Plugin Version: 1.0 Price: Free Source: WordPress.org Files: 16 (408.52kB) Short Codes: [ / ] 0 Database Tables: 0 Function Count: 14 Code Review: Search Provit

Do you need help with Vintage.js? Get professional plugin support here in no time at all

Which new files does Vintage.js add to WordPress?

This section will populate with a table showing an icon, size and filepath.

The plugin Vintage.js added 16 new files when it was installed with WP-CLI in our WordPress test environment.

Type & Path	Size	Conflicts
wp-content/plugins/vintagejs/	408.52kB	No known conflicts with other themes or plugins.
wp-content/plugins/vintagejs/admin/	1.46kB	No known conflicts with other themes or plugins.
wp-content/plugins/vintagejs/admin/admin.php	1.46kB	No known conflicts with other themes or plugins.
wp-content/plugins/vintagejs/bp/		No known conflicts with other themes or plugins.
wp-content/plugins/vintagejs/bp/bp-core.php		No known conflicts with other themes or plugins.
wp-content/plugins/vintagejs/css/	4.83kB	No known conflicts with other themes or plugins.
wp-content/plugins/vintagejs/css/clock.png	4.16kB	No known conflicts with other themes or plugins.
wp-content/plugins/vintagejs/css/vintagejs.css	683.00B	No known conflicts with other themes or plugins.
wp-content/plugins/vintagejs/curves.js	1.70kB	No known conflicts with other themes or plugins.
wp-content/plugins/vintagejs/excanvas.compiled.js	11.10kB	No known conflicts with other themes or plugins.
wp-content/plugins/vintagejs/license.txt	14.77kB	No known conflicts with other themes or plugins.
wp-content/plugins/vintagejs/loader.php	3.68kB	No known conflicts with other themes or plugins.
wp-content/plugins/vintagejs/readme.txt	1.42kB	No known conflicts with other themes or plugins.
wp-content/plugins/vintagejs/screenshot-1.png	47.84kB	No known conflicts with other themes or plugins.
wp-content/plugins/vintagejs/screenshot-2.png	314.74kB	No known conflicts with other themes or plugins.
wp-content/plugins/vintagejs/vintage.min.js	6.99kB	No known conflicts with other themes or plugins.

Which new shortcodes does Vintage.js add to WordPress?

The plugin Vintage.js did not add any shortcodes when it was installed with WP-CLI in our WordPress test environment.

Which new database tables are created by the WordPress plugin Vintage.js?

Vintage.js did not create any new database tables when it was installed. It is possible that the plugin creates new database tables after an initial setup or configuration or after some period of use.

Which new options are added to the wp-options table by Vintage.js?

None. There may be settings which have been changed by installing the Vintage.js plugin however we do not yet track those changes.

What new PHP functions does Vintage.js declare when it is active?

Installing Vintage.js added 14 new functions to Wordpress at run-time. These functions are internal and generally aren't meant to be used except by developpers who wish to interface with the plugin to enhance or alter its behavior.

Function	Conflicts	Common Errors
my_image_attachment_fields_to_edit	1 conflict	Fatal error: Cannot redeclare my_image_attachment_fields_to_edit()
my_image_attachment_fields_to_save	1 conflict	Fatal error: Cannot redeclare my_image_attachment_fields_to_save()
add_class_blnwh	0 conflicts	Fatal error: Cannot redeclare add_class_blnwh()
add_class_sepia	0 conflicts	Fatal error: Cannot redeclare add_class_sepia()
add_class_vintage	0 conflicts	Fatal error: Cannot redeclare add_class_vintage()
bw_image_tag_class	0 conflicts	Fatal error: Cannot redeclare bw_image_tag_class()
sepia_image_tag_class	0 conflicts	Fatal error: Cannot redeclare sepia_image_tag_class()
vintage_image_tag_class	0 conflicts	Fatal error: Cannot redeclare vintage_image_tag_class()
vintagejs_insert_head	0 conflicts	Fatal error: Cannot redeclare vintagejs_insert_head()
vintagejs_plugin_menu	0 conflicts	Fatal error: Cannot redeclare vintagejs_plugin_menu()
vintagejs_plugin_options	0 conflicts	Fatal error: Cannot redeclare vintagejs_plugin_options()
vintagejs_register_settings	0 conflicts	Fatal error: Cannot redeclare vintagejs_register_settings()
vintagejs_scripts	0 conflicts	Fatal error: Cannot redeclare vintagejs_scripts()
vintagejs_styles	0 conflicts	Fatal error: Cannot redeclare vintagejs_styles()

Using Vintage.js from the command line with WP-CLI

The following commands are provided for convenience and should only be used if you understand how WP-CLI works. These commands refer to a single WordPress instance and may need to be modified if you are working with a Multisite installation.

How to install Vintage.js from the command line with WP-CLI

Navigate to the root of your WordPress installation and type the following command:

wp plugin install vintagejs

How to activate Vintage.js from the command line with WP-CLI

To immediately activate Vintage.js after WP-CLI downloads the latest version you can use the following command:

wp plugin install vintagejs --activate

How to reinstall Vintage.js from the command line with WP-CLI

To force a reinstallation of Vintage.js which overwrites the current plugin without asking for confirmation you can use the following command:

wp plugin install vintagejs --force

How to update Vintage.js to the latest version from the command line with WP-CLI

wp plugin update vintagejs

How to delete Vintage.js from the command line with WP-CLI

wp plugin delete vintagejs

Where can you download earlier versions of Vintage.js?

Whenever possible you should use the latest version of plugins and themes, however if you have recently updated and discovered that you need to install an earlier version you may be able to download other versions of Vintage.js from the WordPress repository by visiting this link.

Please note that installing earlier versions of a theme or plugin is not generally a recommended course of action for most users and could re-introduce security, stability or other issues in Vintage.js

About our testing enviroment

Tests were conducted using Apache 2.4.29, PHP 7.2 on Ubuntu 18.04, MySQL 5.7.33 and WordPress 5.9

It is very possible that different versions of PHP such as PHP 8.0, PHP 7.4, or PHP 7.3 could behave differently with Vintage.js. Different versions of WordPress could implement the features of this plugin in slightly different ways as well.