Forum Replies Created

Viewing 15 replies - 46 through 60 (of 77 total)
  • Thread Starter spinhead

    (@spinhead)

    Ta daa. Thanks muchly. Will research kses.

    Note: because this seems to be a day where everyone skips over little assumptions:

    You have to add this element first for this to work.

    By “this element” you mean “the input element”
    By “add” you mean “add to what kses allows”
    And the whole batch goes in functions.php
    Though it’s hard to tell if by “add this . . . first” if it needs to be added to functions.php above/before the shortcode, or simply “do this, then it’ll work.”

    Not trying to be a jerk. Just having a difficult time getting folks to write clear coherent responses to what I believe are clear coherent queries. Your answer is correct, but someone with a tiny bit less information and experience would be back here asking for clarification, perhaps multiple rounds of it.

    Again, thanks for the perfect solution, and a research project that’ll deepen my understanding of this stuff.

    Thread Starter spinhead

    (@spinhead)

    As I mentioned, I’ve perused the wp-cli settings pretty carefully. Checked again, and nothing under “wp user meta list” includes settings for what are apparently called meta boxes.

    It’s not clear where metaboxhidden_dashboard is; I don’t see it in the database or the wp cli functions.

    Thread Starter spinhead

    (@spinhead)

    Code in view source is now

    <input id="<?php do_shortcode( handle[this_post_num]); ?>” type=”checkbox” name=”collapse” /></p>

    In other words, same result, it’s just showing the new code instead of the old.

    Will php really run in a form field in a post? Seems unlikely to me.

    Thread Starter spinhead

    (@spinhead)

    I was pretty sure I explicitly said I was looking to change the dashboard screen options, as in, the drop down from the top that has checkboxes to show/hide the various items on the dashboard. Dunno why it doesn’t say that now, so obviously I misremembered.

    I’ve gone through the entire list of wp cli commands and the database fields and can’t find this information. The Options subcommand doesn’t cover it.

    Thread Starter spinhead

    (@spinhead)

    Huh. It was not there, honest! There now, though.

    However, I was thinking like a developer, not an end user, so I assumed it would affect the Theme Editor. I rarely (almost never) use the Custom CSS tool, which is what this appears to work with.

    Not what I was hoping for. Will continue mass copy/pasting until something better comes along.

    Thread Starter spinhead

    (@spinhead)

    Very much interested, in fact. Help? Hello?

    Thread Starter spinhead

    (@spinhead)

    Still interested in resolving this.

    Thread Starter spinhead

    (@spinhead)

    Updates will probably put back files

    d’oh. of course they will.

    The good news is multisite

    Yup. Got me some studying to do. Excellent. Thanks.

    Thread Starter spinhead

    (@spinhead)

    It happens with any plugin, but doing the update from within the WordPress dashboard works fine, so it’s unlikely to be permissions. Also, the error specifically mentioning both a specific line of code in wp-cli and the return of an http header issue () makes permissions problems seem less likely.

    However, just to confirm, all permissions in the plugins folders are 755 for folders, 644 for files, so that shouldn’t be causing a problem.

    Thread Starter spinhead

    (@spinhead)

    The host changed my account’s path to php and resolved this issue. I’m finding out if it’s something I should have been able to do (user error) or something they had to fix (misconfiguration.)

    Thread Starter spinhead

    (@spinhead)

    A new host because they have tight security? I think not. I’ve been with them for over a decade and received the best customer service, not just of any hosting company, but of any business relationship, in my life.

    But other technical suggestions are welcome 🙂

    Thread Starter spinhead

    (@spinhead)

    phpinfo() is disabled on the server, and with jailedshell I don’t have access outside my hosting directory, nor can I install anything on the server.

    I will confirm with my guy about the php files for the old version. That’s a good question.

    Thank you.

    Thread Starter spinhead

    (@spinhead)

    -jailshell: /usr/bin/su: Permission denied

    My server guy has a query in to his people. He’s never used wp-cli but he has resources to check with. If I need him to do something, he’ll gladly do it barring security issues. But at this point, we’re not even sure what he could change to allow this to work.

    Thanks for continuing to offer suggestions. I appreciate any help I can get.

    Thread Starter spinhead

    (@spinhead)

    PHP version is fine in cPanel, and fine if I check the PHP version in terminal/ssh. Site Health is good.

    If I run

    export WP_CLI_PHP=/opt/php72/bin

    I get no error, which should mean all is well. Then I immediately run

    wp plugin list

    and get back

    Your server is running PHP version 5.5.38 but WordPress 5.3.2 requires at least 5.6.20.

    So wp-cli seems to be ignoring the version of php in my htaccess, the version the site is using, and ignoring the explicit command to use v7.2, and using ONLY the default version on the server.

    I really don’t know. Hopefully the plugin author will drop by someday to address the outstanding support requests.

    Did you try my last suggestion? I think it addresses your need, but if not, perhaps try showing an example.

Viewing 15 replies - 46 through 60 (of 77 total)