Title: CPKN's Replies | WordPress.org

---

# CPKN

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

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

 Search replies:

## Forum Replies Created

Viewing 15 replies - 1 through 15 (of 27 total)

1 [2](https://wordpress.org/support/users/cpkn/replies/page/2/?output_format=md)
[→](https://wordpress.org/support/users/cpkn/replies/page/2/?output_format=md)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[NextScripts: Social Networks Auto-Poster] Forced to post as visitor](https://wordpress.org/support/topic/forced-to-post-as-visitor/)
 *  [CPKN](https://wordpress.org/support/users/cpkn/)
 * (@cpkn)
 * [8 years, 2 months ago](https://wordpress.org/support/topic/forced-to-post-as-visitor/page/2/#post-10160516)
 * Hey guys,
 * I guess ill throw in my 2 cents.
 * I actually haven’t been active in my posts since December last year, due to a
   rethink in my posts and planning the upgrade of my site.
 * Due to this, I never really kept up with the changes of Facebook and SNAP.
 * The plugin had a very old API and was basically dead in the water.
 * So today, what I did was delete my old App and recreate the App.
 * I followed the Instructions to ensure I didn’t miss anything, I even had to make
   my site HTTPS coz API’s from Facebook force HTTPS now.
 * and once I was done, I really didn’t pay attention to the “where/who to” drop
   down. So My test posts were going into the Visitor Area as my actual Facebook.
 * Once I found out I must change to post to my Page, thats where this threads issue
   remains.
 * Despite all my settings set up correctly, it still posts to as my actual Account
   to the Visitor Section and not as my Page, on the Page.
 * You will see by this post date that it still hasn’t been resolved.
 * So far, the plugin has had no error, so I assume its Facebook that is messing
   up.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Conditional Fields for Contact Form 7] Plugin Edit Field is missing](https://wordpress.org/support/topic/plugin-edit-field-is-missing/)
 *  Thread Starter [CPKN](https://wordpress.org/support/users/cpkn/)
 * (@cpkn)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/plugin-edit-field-is-missing/#post-9119690)
 * Yep,
 * That works!
 * Thanks heaps!
 * I won’t update til I get everything updated. My theme has finally been updated
   to be compatible with 4.7.# so I can now get everything up-to-date and have your
   plugin function how it suppose to.
 * Thanks heaps
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Conditional Fields for Contact Form 7] Plugin Edit Field is missing](https://wordpress.org/support/topic/plugin-edit-field-is-missing/)
 *  Thread Starter [CPKN](https://wordpress.org/support/users/cpkn/)
 * (@cpkn)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/plugin-edit-field-is-missing/#post-9119676)
 * Hey,
 * right, the email read like this (which I copied and pasted):
 * “26: $all_fields = “$post->form_scan_shortcode();””
    “39: $all_groups = “$post-
   >form_scan_shortcode(array(‘type’=>’group’));””
 * But I see it is now better looking with the forum lolz
 * Edit: Ok, the forum keeps correcting it lolz. so the email shows “$post-&gt” 
   not the proper code.
    -  This reply was modified 9 years, 1 month ago by [CPKN](https://wordpress.org/support/users/cpkn/).
    -  This reply was modified 9 years, 1 month ago by [CPKN](https://wordpress.org/support/users/cpkn/).
    -  This reply was modified 9 years, 1 month ago by [CPKN](https://wordpress.org/support/users/cpkn/).
    -  This reply was modified 9 years, 1 month ago by [CPKN](https://wordpress.org/support/users/cpkn/).
    -  This reply was modified 9 years, 1 month ago by [CPKN](https://wordpress.org/support/users/cpkn/).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Conditional Fields for Contact Form 7] Plugin Edit Field is missing](https://wordpress.org/support/topic/plugin-edit-field-is-missing/)
 *  Thread Starter [CPKN](https://wordpress.org/support/users/cpkn/)
 * (@cpkn)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/plugin-edit-field-is-missing/#post-9119595)
 * For some reason, I get this:
 * > Parse error: syntax error, unexpected ‘&’ in …/wp-content/plugins/cf7-conditional-
   > fields/admin.php on line 26
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Conditional Fields for Contact Form 7] Plugin Edit Field is missing](https://wordpress.org/support/topic/plugin-edit-field-is-missing/)
 *  Thread Starter [CPKN](https://wordpress.org/support/users/cpkn/)
 * (@cpkn)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/plugin-edit-field-is-missing/#post-9115282)
 * Yes, you are right.
 * It would seem it is considered as “up-to-date” because the latest CF7 is not 
   compatible with my WP version. I am a lower version due to theme Dev not making
   updates for it fast enough.
 * Note that I consider making an upgrade, but I am still in planning phase.
 * So unless I install the latest CF7 and hope it does work, I guess it is a matter
   of reverting back your plugin version that matches compatibility with my version(
   CF7 4.4.2).
 * Please advise?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Conditional Fields for Contact Form 7] Plugin Edit Field is missing](https://wordpress.org/support/topic/plugin-edit-field-is-missing/)
 *  Thread Starter [CPKN](https://wordpress.org/support/users/cpkn/)
 * (@cpkn)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/plugin-edit-field-is-missing/#post-9112231)
 * Hey,
 * I found the issue! Debug shows Error…
 * > PHP Fatal Error: Call to undefined method WPCF7_ContactForm::scan_form_tags()
   > in –Private–/plugins/cf7-conditional-fields/admin.php on line 24
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Conditional Fields for Contact Form 7] Plugin Edit Field is missing](https://wordpress.org/support/topic/plugin-edit-field-is-missing/)
 *  Thread Starter [CPKN](https://wordpress.org/support/users/cpkn/)
 * (@cpkn)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/plugin-edit-field-is-missing/#post-9110734)
 * Hey,
 * thanks for that.
 * Sorry, just a heads up that I will be delayed on your next troubleshooting step.
   Busy Busy.
 * Hopefully will be done within 24 hours.
 * Cheers for your help so far! You are the first Dev that actually puts the effort
   into detailed help and instructions and I love it!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Conditional Fields for Contact Form 7] Plugin Edit Field is missing](https://wordpress.org/support/topic/plugin-edit-field-is-missing/)
 *  Thread Starter [CPKN](https://wordpress.org/support/users/cpkn/)
 * (@cpkn)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/plugin-edit-field-is-missing/#post-9107135)
 * Hello,
 * Thanks for the reply.
 * No Java errors at all.
 * You will see what I mean in the picture.
 * ![Editor looks like this in the form](https://i0.wp.com/cpkncomputers.com.au/
   wp-content/uploads/2017/05/Screenshot-1.png)
    -  This reply was modified 9 years, 1 month ago by [CPKN](https://wordpress.org/support/users/cpkn/).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[NextScripts: Social Networks Auto-Poster] Graph API v2.1 Upgrade Notice](https://wordpress.org/support/topic/graph-api-v21-upgrade-notice/)
 *  [CPKN](https://wordpress.org/support/users/cpkn/)
 * (@cpkn)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/graph-api-v21-upgrade-notice/#post-7503803)
 * Hello,
 * I would like to add myself to this question. I too have this message.
 * All documents I found for you guys talk about API OAuth ver. 2.0.
 * Please note that I opened a ticket also.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Popup Maker - Boost Sales, Conversions, Optins, Subscribers with the Ultimate WP Popup Builder] Update & Activating 1.4.7 causes Fatal Error](https://wordpress.org/support/topic/update-activating-147-causes-fatal-error/)
 *  Thread Starter [CPKN](https://wordpress.org/support/users/cpkn/)
 * (@cpkn)
 * [10 years ago](https://wordpress.org/support/topic/update-activating-147-causes-fatal-error/#post-7319275)
 * Hello,
 * I didn’t see it show 2 different plugins. whoops!
 * I will disable both and try again.
 * If it helps, what is the next step for me? do you know the specific issues for
   me to get the other plugin devs to help, or do you have something that could 
   help? Especially since the current version I have has no issues (1.3.9).
 * I will hopefully get an update within 24hrs on here.
 * [@mrcarllister](https://wordpress.org/support/users/mrcarllister/) Sorry to hear
   you have issues. Please do create a new ticket with [@danieliser](https://wordpress.org/support/users/danieliser/)
   so you can get it solved.
 * The error logging can be tricky if you don’t know much about changing code in
   WP files, FTP and if there is another underlining issue like I had the first 
   time.
 * Best of luck.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Popup Maker - Boost Sales, Conversions, Optins, Subscribers with the Ultimate WP Popup Builder] Update & Activating 1.4.7 causes Fatal Error](https://wordpress.org/support/topic/update-activating-147-causes-fatal-error/)
 *  Thread Starter [CPKN](https://wordpress.org/support/users/cpkn/)
 * (@cpkn)
 * [10 years ago](https://wordpress.org/support/topic/update-activating-147-causes-fatal-error/#post-7319271)
 * Hello,
 * I am finally back!
 * So some good news, and bad news 🙁
 * Good News – When updating to latest update, the fatal error did not appear.
 * Bad News – A message popup from your plugin asked for me to update the database.
   It went through rebuilding data, pop up targeting conditions etc. As soon as 
   it did it, the fatal error appeared.
 * Good News – It does not kill the whole site, it has fatal error when trying to
   access the plugin settings.
 * More Good News – I figured out how to get the WP Debug to work and I have more
   info now. It looks like it could definitely be a plugin conflict, but when I 
   deactivate the mentioned plugin, it doesn’t fix the error:
 * >  Strict Standards: Declaration of c2c_ConfigureSMTP::options_page_description()
   > should be compatible with C2C_Plugin_023::options_page_description($localized_heading_text
   > = ”) in …/plugins/configure-smtp/configure-smtp.php on line 47
   > Fatal error: Call to a member function get() on null in …/wp-includes/query.
   > php on line 27
   > Notice: is_home was called incorrectly. Conditional query tags do not work 
   > before the query is run. Before then, they always return false. Please see 
   > Debugging in WordPress for more information. (This message was added in version
   > 3.1.) in …/wp-includes/functions.php on line 3622
   > Notice: is_front_page was called incorrectly. Conditional query tags do not
   > work before the query is run. Before then, they always return false. Please
   > see Debugging in WordPress for more information. (This message was added in
   > version 3.1.) in …/wp-includes/functions.php on line 3622
 * Not sure what you can make of it.
 * I did also try the backtrace again, I think I got it to work, this is what I 
   got:
 * >  Backtrace from warning ‘Declaration of c2c_ConfigureSMTP::options_page_description()
   > should be compatible with C2C_Plugin_023::options_page_description($localized_heading_text
   > = ”)’ at …/wp-content/plugins/configure-smtp/configure-smtp.php 47:
   >  1. …/wp-
   > settings.php 215 calling include_once() 2. …/wp-config.php 236 calling require_once()
   > 3. …/wp-load.php 37 calling require_once() 4. …/wp-admin/admin.php 31 calling
   > require_once() 5. …/wp-admin/edit.php 10 calling require_once()
   > Fatal error: Call to a member function get() on null in …/wp-includes/query.
   > php on line 27
   > Backtrace from warning ‘is_home was called incorrectly. Conditional query tags
   > do not work before the query is run. Before then, they always return false.
   > Please see Debugging in WordPress for more information. (This message was added
   > in version 3.1.)’ at …/wp-includes/functions.php 3622:
   >  1. …/wp-includes/functions.
   > php 3622 calling trigger_error() 2. …/wp-includes/query.php 447 calling _doing_it_wrong()
   > 3. …/wp-content/plugins/social-networks-auto-poster-facebook-twitter-g/nxs_functions.
   > php 1140 calling is_home() 4. calling nxs_psCron() 5. …/wp-includes/plugin.
   > php 503 calling call_user_func_array() 6. …/wp-includes/load.php 611 calling
   > do_action() 7. calling shutdown_action_hook()
   > Backtrace from warning ‘is_front_page was called incorrectly. Conditional query
   > tags do not work before the query is run. Before then, they always return false.
   > Please see Debugging in WordPress for more information. (This message was added
   > in version 3.1.)’ at …/wp-includes/functions.php 3622:
   >  1. …/wp-includes/functions.
   > php 3622 calling trigger_error() 2. …/wp-includes/query.php 418 calling _doing_it_wrong()
   > 3. …/wp-content/plugins/social-networks-auto-poster-facebook-twitter-g/nxs_functions.
   > php 1140 calling is_front_page() 4. calling nxs_psCron() 5. …/wp-includes/plugin.
   > php 503 calling call_user_func_array() 6. …/wp-includes/load.php 611 calling
   > do_action() 7. calling shutdown_action_hook()
 * Well I hope this is what you are looking for and helps!
 * Chris
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Popup Maker - Boost Sales, Conversions, Optins, Subscribers with the Ultimate WP Popup Builder] Feature Suggestion (Close Actions)](https://wordpress.org/support/topic/feature-suggestion-close-actions/)
 *  Thread Starter [CPKN](https://wordpress.org/support/users/cpkn/)
 * (@cpkn)
 * [10 years, 1 month ago](https://wordpress.org/support/topic/feature-suggestion-close-actions/#post-7339209)
 * Hello,
 * Well, I completely forgot about the theme editor… Amazeballs!
 * If getting the “accordion” and animations, and it was made real good, for $10-
   20 just to get those features, I would buy, NO WORRIES!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Popup Maker - Boost Sales, Conversions, Optins, Subscribers with the Ultimate WP Popup Builder] Update & Activating 1.4.7 causes Fatal Error](https://wordpress.org/support/topic/update-activating-147-causes-fatal-error/)
 *  Thread Starter [CPKN](https://wordpress.org/support/users/cpkn/)
 * (@cpkn)
 * [10 years, 1 month ago](https://wordpress.org/support/topic/update-activating-147-causes-fatal-error/#post-7319218)
 * Hello,
 * Yes, I see you made some updates… Awesome!. I will see if its ok with the latest.
 * As far as the plugin conflict, I will check what you said about activating and
   see and update you, if the latest update does not work of course.
 * Thanks!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Popup Maker - Boost Sales, Conversions, Optins, Subscribers with the Ultimate WP Popup Builder] Update & Activating 1.4.7 causes Fatal Error](https://wordpress.org/support/topic/update-activating-147-causes-fatal-error/)
 *  Thread Starter [CPKN](https://wordpress.org/support/users/cpkn/)
 * (@cpkn)
 * [10 years, 1 month ago](https://wordpress.org/support/topic/update-activating-147-causes-fatal-error/#post-7319212)
 * Hey,
 * I haven’t had any luck in getting the Stacktrace to work.
 * There is a few more things I can try but busy times are getting in the way.
 * I hope the other reports can help you with this issue.
 * I will keep you posted on getting the trace.
 * Sorry for the delay.
 * Cheers!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Popup Maker - Boost Sales, Conversions, Optins, Subscribers with the Ultimate WP Popup Builder] Update & Activating 1.4.7 causes Fatal Error](https://wordpress.org/support/topic/update-activating-147-causes-fatal-error/)
 *  Thread Starter [CPKN](https://wordpress.org/support/users/cpkn/)
 * (@cpkn)
 * [10 years, 1 month ago](https://wordpress.org/support/topic/update-activating-147-causes-fatal-error/#post-7319133)
 * Hello,
 * So had a bit of a bump getting the code to work, but then I thought I had it 
   until I new error came up:
 * > Fatal error: Call to undefined function nocache_headers() in …/wp-admin/admin.
   > php on line 33
 * Line 33 is literally
 * > nocache_headers()
 * Dunno why this affects it when adding the code but otherwise is fine?
 * I will try again when I can later today/tonight (currently 12:30pm), if you have
   any ideas on what I have done wrong, let me know.
 * I will keep you posted.
 * Note: I can remove the line of code in query.php to get my website running without
   WSOD, but as I am not pro with this sort of thing, I don’t know if that would
   be bad to keep out for the long term.

Viewing 15 replies - 1 through 15 (of 27 total)

1 [2](https://wordpress.org/support/users/cpkn/replies/page/2/?output_format=md)
[→](https://wordpress.org/support/users/cpkn/replies/page/2/?output_format=md)