Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
TDBF Posted October 4, 2020 Posted October 4, 2020 When in Developer mode, if I upload a plug-in, the developer (Dev directory) files are created (Manual upload), however the css files are created in the css folder. However, the CSS styles can be found in the theme ACP. Also, I have found that sometimes the version files in setup don't always get created either on install..
bfarber Posted October 5, 2020 Posted October 5, 2020 18 hours ago, TDBF said: however the css files are created in the css folder. Are you saying they aren't created? Because I'm unclear otherwise if this wasn't a typo?
TDBF Posted October 5, 2020 Author Posted October 5, 2020 21 minutes ago, bfarber said: Are you saying they aren't created? Because I'm unclear otherwise if this wasn't a typo? Sorry, they are not created.
bfarber Posted October 6, 2020 Posted October 6, 2020 I've opened a report internally to check on this. Thanks.
PurplePixel Posted January 8, 2021 Posted January 8, 2021 @bfarber getting the same issue - please see below The following conditional fails in `system/Theme/Theme.php` - line 4882 // create the plugin template if( \IPS\IN_DEV AND $data['app'] === 'core' AND $data['location'] === 'custom' AND $data['path'] === 'front' AND isset( $data['plugin'] ) ) { $plugin = \IPS\Plugin::load( $data['plugin'] ); \file_put_contents( \IPS\ROOT_PATH . "/plugins/{$plugin->location}/dev/css/{$data['name']}", $data['content'] ); @chmod( \IPS\ROOT_PATH . "/plugins/{$plugin->location}/dev/css/{$data['name']}", \IPS\IPS_FILE_PERMISSION ); } Why? When you do manual upload the variables are set incorrectly. `applications/core/modules/admin/applications/plugins.php` - line 681 $class::addCss( array( 'app' => 'core', 'location' => 'front', 'path' => 'custom', 'name' => $xml->getAttribute('filename'), 'content' => base64_decode( $xml->readString() ), 'plugin' => $plugin->id ), TRUE ); Please look at `location` and `path`.
Solution bfarber Posted January 11, 2021 Solution Posted January 11, 2021 Yes, this is already fixed for our upcoming 4.6 release. 👍
Recommended Posts