network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year |
| seen | Mar 30 at 10:30 | |
| stats | profile views | 4 |
An "older developer" who got out of coding and into senior management but has decided to come back out of the clouds and get dirty again with code. Happy days. :^)
|
Feb 17 |
revised |
DB access blocked when initializing WP externally deleted 12 characters in body |
|
Feb 17 |
accepted | DB access blocked when initializing WP externally |
|
Feb 17 |
answered | DB access blocked when initializing WP externally |
|
Feb 12 |
comment |
DB access blocked when initializing WP externally I used the host/database/username/password from the wp-config.php file on the command line and it connected fine. Also the wp-config.php works fine when run via Wordpress screens. |
|
Feb 11 |
asked | DB access blocked when initializing WP externally |
|
Feb 1 |
accepted | Including Wordpress in RESTful API |
|
Jan 29 |
comment |
Including Wordpress in RESTful API Yes this is the problem with the whitelisting approach. I'm still secretly hoping to find an innovative way to default it to the global namespace but until that day this list is a good start and if you have any further exceptions you can hopefully pick them off pretty quickly. For me it was just adding one that my theme needed and it seems to work in all the use-cases I need. |
|
Jan 29 |
awarded | Teacher |
|
Jan 28 |
revised |
Including Wordpress in RESTful API added 285 characters in body |
|
Jan 28 |
comment |
Including Wordpress in RESTful API I am going to look a little more into namespacing and see if there isn't a more global scoping directive that could be used. |
|
Jan 28 |
answered | Including Wordpress in RESTful API |
|
Jan 28 |
revised |
Including Wordpress in RESTful API added 541 characters in body |
|
Jan 28 |
comment |
Including Wordpress in RESTful API @kaiser, the WP stuff I've seen -- including the link you've sent -- is pretty dated. As for XML RPC versus REST ... the momentum seems to be toward REST and my goal is to make integration with my platform as easy as possible. As for being a "true" RESTful service or just an HTTP-based data interface ... my goal is to be RESTful but there might be a few compromises that the purists would not be happy with. It's a touchy area. :^) |
|
Jan 28 |
comment |
Including Wordpress in RESTful API @Wyck, I think you're line of thinking is going in the right direction but can I ask for a little more of your thinking? Are imports done inside function blocks initialised differently? Is there possibly a namespace issue here (shooting in the dark), etc.? |
|
Jan 28 |
comment |
Including Wordpress in RESTful API @MarkKaplun, I've run a stacktrace on the errors and they terminate in the query.php function in wp-includes and are called by my theme's library. That said, I think the problem isn't solving this call but understanding why the variation in state exists between the import statement when it's outside of a function call versus inside it. |
|
Jan 28 |
asked | Including Wordpress in RESTful API |
|
Jan 20 |
accepted | Nuance in adding CPT and TAX to a submenu |
|
Jan 20 |
answered | Nuance in adding CPT and TAX to a submenu |
|
Nov 14 |
awarded | Tumbleweed |
|
Nov 10 |
awarded | Commentator |
