Why is this plugin so BAD

  • At this stage this plugin is a total bug fest. It would be great if it worked. Almost nothing works as shown. Can’t import it’s own child themes. Can’t write to local fonts. And when you manually FTP your new font into the right folder and edit the theme.json file it works. For a day. Then for whatever reason the next day – only one font variation will work. Double checked everything. Re uploaded new theme.json. Because I need PT Sans Narrow to work with the regular and bold (for squeezing headings in) this is a pain. The only fix I could come up with was to edit theme.json with the Bold PT Sans Narrow renamed as ‘my-swear-word-font’. That worked. Still can’t export a child theme after the update. And to think the TOP MAN at WordPress flouted this.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Matias Benedetto

    (@mmaattiiaass)

    Hi @berternie I’m sorry that the plugin is not working as expected for you.
    I would need more info to try to help you.
    Could you share this info about your current setup?:
    – browser
    – operative system
    – server
    – how are you running your WordPress
    – the contents of your wp-config file (please don’t share the authentication unique keys and salts part).

    Thanks!

    Thread Starter berternie

    (@berternie)

    -browser Chrome
    -Win 10
    -nginx
    -local setup (using local) as well on live sites
    -fresh install using greenshift theme and the greenshift plugin. And with no use of their font features. A basic raw install. Again with multiple sites l(live and local). I appreciate the time and effort you put in but after seeing that Mullenweg bloke demo it (and others) I thought I would give it a go. And after spending about a dozen hours – I gave up.

    On my local basic install (Fresh install with Greenshift theme and plugin) I was so disappointed with the plugin I deleted it. Just to try it again I added it back in. Seen it was recently updated. Tried to add a font. Still doesn’t work. Almost nothing worked – and I tried everything. New installs (on local). Read everything I could find. Can’t install a font or write a theme (multiple variations were tried}. The only thing I could get to work was by manually uploading the font to the appropriate folder… and even then there were numerous issues.

    <?php

/**

 * The base configuration for WordPress

 *

 * The wp-config.php creation script uses this file during the installation.

 * You don't have to use the web site, you can copy this file to "wp-config.php"

 * and fill in the values.

 *

 * This file contains the following configurations:

 *

 * * Database settings

 * * Secret keys

 * * Database table prefix

 * * Localized language

 * * ABSPATH

 *

 * @link https://www.ads-software.com/support/article/editing-wp-config-php/

 *

 * @package WordPress

 */

// ** Database settings - You can get this info from your web host ** //

/** The name of the database for WordPress */

define( 'DB_NAME', 'local' );

/** Database username */

define( 'DB_USER', 'root' );

/** Database password */

define( 'DB_PASSWORD', 'root' );

/** Database hostname */

define( 'DB_HOST', 'localhost' );

/** Database charset to use in creating database tables. */

define( 'DB_CHARSET', 'utf8' );

/** The database collate type. Don't change this if in doubt. */

define( 'DB_COLLATE', '' );

/**#@+

 * Authentication unique keys and salts.

 *

 * Change these to different unique phrases! You can generate these using

 * the {@link https://api.www.ads-software.com/secret-key/1.1/salt/ www.ads-software.com secret-key service}.

 *

 * You can change these at any point in time to invalidate all existing cookies.

 * This will force all users to have to log in again.

 *

 * @since 2.6.0

 */

/**#@-*/

/**

 * WordPress database table prefix.

 *

 * You can have multiple installations in one database if you give each

 * a unique prefix. Only numbers, letters, and underscores please!

 */

$table_prefix = 'wp_';

/* Add any custom values between this line and the "stop editing" line. */

/**

 * For developers: WordPress debugging mode.

 *

 * Change this to true to enable the display of notices during development.

 * It is strongly recommended that plugin and theme developers use WP_DEBUG

 * in their development environments.

 *

 * For information on other constants that can be used for debugging,

 * visit the documentation.

 *

 * @link https://www.ads-software.com/support/article/debugging-in-wordpress/

 */

if ( ! defined( 'WP_DEBUG' ) ) {

    define( 'WP_DEBUG', false );

}

/* That's all, stop editing! Happy publishing. */

/** Absolute path to the WordPress directory. */

if ( ! defined( 'ABSPATH' ) ) {

    define( 'ABSPATH', __DIR__ . '/' );

}

/** Sets up WordPress vars and included files. */

require_once ABSPATH . 'wp-settings.php';
    Plugin Author Matias Benedetto

    (@mmaattiiaass)

    I understand your frustration. I’m not a Windows and Local user, but I got a windows machine and Installed Local on it. I was able to reproduce the same error (lack of writing permissions on the theme folder).

    The error is not a result of a bug in the plugin but the result of the lack of file permissions on the server. If the server doesn’t have permission to write the file, the plugin can’t do anything about this situation; it just warns you about the error. If any plugin or PHP script could change file permissions in the filesystem, the security problems would be massive. The operative system handles the file permissions.

    I don’t know this data is up-to-date but, as far as I can read in the Local forums there problem is the following one:
    Local uses Docker under the hood to run the sites. What Docker does is load “containers”, a kind of virtual machine, to run the MYSQL and web server (Apache or Nginx) needed to execute WordPress inside it. The problem is that as this entire web environment runs inside the containers, you can’t easily change what happens inside those containers.

    Can I change the file permissions of my themes folder using the Windows file explorer? Yes, you can, but those changes will be ignored. Why? When you run Docker the files used by the container are handled by Docker and their own set of user permissions because it is as if it is another machine. You would need to enter the container and modify the file permissions of the folders inside it.

    How to connect to the docker instance running the Nginx/apache server and modify the file permissions of the theme folder using Local on Windows? That’s the not easy question we need to solve this problem. I searched for it in the Local forums and didn’t find a good answer.

    Meanwhile, what I may suggest is to run WordPress in a different way (not virtualized as with Local/Docker) on your Windows machine.

    If something of this needs to be clarified, or you need help with something else, let me know!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Why is this plugin so BAD’ is closed to new replies.