Title: eigood's Replies | WordPress.org

---

# eigood

  [  ](https://wordpress.org/support/users/eigood/)

 *   [Profile](https://wordpress.org/support/users/eigood/)
 *   [Topics Started](https://wordpress.org/support/users/eigood/topics/)
 *   [Replies Created](https://wordpress.org/support/users/eigood/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/eigood/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/eigood/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/eigood/engagements/)
 *   [Favorites](https://wordpress.org/support/users/eigood/favorites/)

 Search replies:

## Forum Replies Created

Viewing 10 replies - 1 through 10 (of 10 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Insert Pages] Privacy protections added in 3.7.0 break direct shortcode calls](https://wordpress.org/support/topic/privacy-protections-added-in-3-7-0-break-direct-shortcode-calls/)
 *  Thread Starter [eigood](https://wordpress.org/support/users/eigood/)
 * (@eigood)
 * [3 years, 11 months ago](https://wordpress.org/support/topic/privacy-protections-added-in-3-7-0-break-direct-shortcode-calls/#post-15779508)
 * So, yeah no. If I switch to “normal” mode, then when I do page=”/path/_nav”, 
   I actually get a re-insertion of the *current* page I’m looking at. If I stay
   with “legacy”. and use my patch, I actually get the referenced page. So normal
   mode doesn’t look at given page attribute at all.
 * Looking further at the code, line 426 contains the same security check as mentioned
   previously, but in this case, it happens *above* the wpip_insert_method condition.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Insert Pages] Privacy protections added in 3.7.0 break direct shortcode calls](https://wordpress.org/support/topic/privacy-protections-added-in-3-7-0-break-direct-shortcode-calls/)
 *  Thread Starter [eigood](https://wordpress.org/support/users/eigood/)
 * (@eigood)
 * [3 years, 11 months ago](https://wordpress.org/support/topic/privacy-protections-added-in-3-7-0-break-direct-shortcode-calls/#post-15779476)
 * That’s got it; it wasn’t clear that your suggestion was to update in the global
   settings area, instead of just setting a new option on the shortcode itself.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Insert Pages] Privacy protections added in 3.7.0 break direct shortcode calls](https://wordpress.org/support/topic/privacy-protections-added-in-3-7-0-break-direct-shortcode-calls/)
 *  Thread Starter [eigood](https://wordpress.org/support/users/eigood/)
 * (@eigood)
 * [3 years, 11 months ago](https://wordpress.org/support/topic/privacy-protections-added-in-3-7-0-break-direct-shortcode-calls/#post-15779469)
 * I take it back, that does *not* work.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Insert Pages] Privacy protections added in 3.7.0 break direct shortcode calls](https://wordpress.org/support/topic/privacy-protections-added-in-3-7-0-break-direct-shortcode-calls/)
 *  Thread Starter [eigood](https://wordpress.org/support/users/eigood/)
 * (@eigood)
 * [3 years, 11 months ago](https://wordpress.org/support/topic/privacy-protections-added-in-3-7-0-break-direct-shortcode-calls/#post-15779467)
 * wpip_insert_method=”normal” works, but can’t users themselves set that parameter
   inside post content areas?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Insert Pages] Privacy protections added in 3.7.0 break direct shortcode calls](https://wordpress.org/support/topic/privacy-protections-added-in-3-7-0-break-direct-shortcode-calls/)
 *  Thread Starter [eigood](https://wordpress.org/support/users/eigood/)
 * (@eigood)
 * [3 years, 11 months ago](https://wordpress.org/support/topic/privacy-protections-added-in-3-7-0-break-direct-shortcode-calls/#post-15765874)
 *     ```
       diff --git a/www/wp-content/plugins/insert-pages/insert-pages.php b/www/wp-content/plugins/insert-pages/insert-pages.php
       index b462d24c..9412e583 100644
       --- a/www/wp-content/plugins/insert-pages/insert-pages.php
       +++ b/www/wp-content/plugins/insert-pages/insert-pages.php
       @@ -746,7 +746,7 @@ if ( ! class_exists( 'InsertPagesPlugin' ) ) {
                                       if ( have_posts() ) {
                                               $can_read = true;
                                               $parent_post_author_id = intval( get_the_author_meta( 'ID' ) );
       -                                       foreach ( $posts as $post ) {
       +                                       if ($parent_post_author_id) foreach ( $posts as $post ) {
                                                       $post_type = get_post_type_object( $post->post_type );
                                                       if ( ! user_can( $parent_post_author_id, $post_type->cap->read_post, $post->ID ) ) {
                                                               $can_read = false;
       ```
   
 * `
    -  This reply was modified 3 years, 11 months ago by [eigood](https://wordpress.org/support/users/eigood/).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Stock Quote] Can no longer list the %ltrade% value](https://wordpress.org/support/topic/can-no-longer-list-the-ltrade-value/)
 *  Thread Starter [eigood](https://wordpress.org/support/users/eigood/)
 * (@eigood)
 * [7 years, 9 months ago](https://wordpress.org/support/topic/can-no-longer-list-the-ltrade-value/#post-10644162)
 * I can do some work on this; for 0.1.7.1, I also had implemented a background 
   type fetch, as originally it would block the main php process, and under heavy
   load, when the cache became invalid, there would be a storm of updates. I did
   it with a system-level cron, tho.
 * The timeline required by the client needs me to move on, but I can work on this
   in my spare time.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Stock Quote] Fix for api breakage](https://wordpress.org/support/topic/fix-for-api-breakage/)
 *  Thread Starter [eigood](https://wordpress.org/support/users/eigood/)
 * (@eigood)
 * [8 years, 9 months ago](https://wordpress.org/support/topic/fix-for-api-breakage/#post-9490074)
 * At least 1.c is bad, for a wordpress plugin. But actually, section 1 says you
   can charge, but then 1.c rescinds that. Very odd. But we must err on the side
   of caution, so I agree that IEX is out.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Stock Quote] Fix for api breakage](https://wordpress.org/support/topic/fix-for-api-breakage/)
 *  Thread Starter [eigood](https://wordpress.org/support/users/eigood/)
 * (@eigood)
 * [8 years, 9 months ago](https://wordpress.org/support/topic/fix-for-api-breakage/#post-9487251)
 * Or: [https://iextrading.com/developer/docs/](https://iextrading.com/developer/docs/)
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Stock Quote] Fix for api breakage](https://wordpress.org/support/topic/fix-for-api-breakage/)
 *  Thread Starter [eigood](https://wordpress.org/support/users/eigood/)
 * (@eigood)
 * [8 years, 9 months ago](https://wordpress.org/support/topic/fix-for-api-breakage/#post-9486634)
 * I’d rather not, as the author has said it’s not allowed for an official plugin.
   I want to honor his recommendation.
 * However, it wasn’t that hard to figure out the correct fields to request, and
   to then parse the csv and convert it to stdClass instance.
 * I’m currently looking at [https://www.alphavantage.co/](https://www.alphavantage.co/),
   but this requires an API key. That’d mean the plugin would need to have a config
   value for that key.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Stock Quote] Fix for api breakage](https://wordpress.org/support/topic/fix-for-api-breakage/)
 *  Thread Starter [eigood](https://wordpress.org/support/users/eigood/)
 * (@eigood)
 * [8 years, 9 months ago](https://wordpress.org/support/topic/fix-for-api-breakage/#post-9480991)
 * Bother. Then my fix will work for my client for the weekend, at least. I’ll look
   more next week.

Viewing 10 replies - 1 through 10 (of 10 total)