Closed tnorthcutt closed 10 years ago
@tnorthcutt Good catch. Seems like there are some differences in how json is structured between different versions of WP-CLI
.
@tnorthcutt Can you verify the JSON you linked to is correctly pasted? I'm seeing some trailing characters after the final closing brace. Specifically the trailing, tle=\"Calendar
characters.
Btw, I'm using this tool to check the json.
@tnorthcutt I have made the WpCli json parser little more resilient to invalid json. This should get rid of your error. But the :Wfoo
commands aren't likely to work until we figure out the reason for the invalid json.
Please update to 0.1.16
and confirm.
@dsawardekar You're right, I messed something up when pasting the json output. I inadvertently added the extra trailing characters. Here's the correct output:
I'm not 100% sure of the correct way to update WP-CLI when it's running in VVV, actually. Do you know if I should just do a git pull
of VVV and then run vagrant provision
?
@tnorthcutt I was referring to updating WordPress.vim to 0.1.16
or 0.1.17
. :) I made some changes to make json parsing more robust that might fix the bug.
Not sure if git pull
of VVV will bring in the latest WP-CLI. I tend to ssh into /srv/www/wp-cli
and git pull origin master
.
Ahh, that confused me, sorry.
I now don't see the error on startup, but I am seeing some bugginess related to the Generating CTAGS ... DONE
message. I'll dig some more and report in the appropriate issue.
As mentioned in issue #12, I'm seeing some errors when I first start Vim:
Pressing
ENTER
clears the errors, and after that I seeWordPress: Loading ... DONE
.As requested, here are the results of running
wp cli cmd-dump
(actually, since I'm using VVV, this is the result of runningvassh wp cli cmd-dump
): https://gist.githubusercontent.com/tnorthcutt/b95dc817fc09c35571cf/raw/34c8e2a6b3bf11d4826e84f586960f3f652aaa5f/wp%20cli%20cmd-dumpThis is with version 0.1.8 of WordPress.vim and version 0.15.1 of WP-CLI.