Title: webbtj's Replies | WordPress.org

---

# webbtj

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

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

 Search replies:

## Forum Replies Created

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

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Flexo Facebook Manager] Comments Error](https://wordpress.org/support/topic/comments-error-9/)
 *  [webbtj](https://wordpress.org/support/users/webbtj/)
 * (@webbtj)
 * [12 years, 6 months ago](https://wordpress.org/support/topic/comments-error-9/#post-4269638)
 * Hi again, so my solution was simply to stop urlencode-ing the data-href attributed
   of the fb-comments box. I haven’t dug into your plugin but hopefully that points
   you in the right direction.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Flexo Facebook Manager] Comments Error](https://wordpress.org/support/topic/comments-error-9/)
 *  [webbtj](https://wordpress.org/support/users/webbtj/)
 * (@webbtj)
 * [12 years, 6 months ago](https://wordpress.org/support/topic/comments-error-9/#post-4269637)
 * Just in case it hasn’t been noted yet, it seems as though this is broken again.
   I’m not using this plugin myself, but when I find the solution I’ll share.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Register Plus Redux] Data Migration from 3.7.3 to 3.9.8](https://wordpress.org/support/topic/data-migration-from-373-to-398/)
 *  Thread Starter [webbtj](https://wordpress.org/support/users/webbtj/)
 * (@webbtj)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/data-migration-from-373-to-398/#post-3551080)
 * Excellent, yeah I managed to get through it myself with some SQL, but it’ll be
   great for the community to have this resolved.
 * Thanks!
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Suddenly my "wp-admin" login page won't load](https://wordpress.org/support/topic/suddenly-my-wp-admin-login-page-wont-load/)
 *  [webbtj](https://wordpress.org/support/users/webbtj/)
 * (@webbtj)
 * [13 years, 4 months ago](https://wordpress.org/support/topic/suddenly-my-wp-admin-login-page-wont-load/#post-3453143)
 * If you have access to your php error logs I would suggest checking there first.
   If you’re not a programmer or other nerd type you could post the last 20 lines
   or so of your error_log here. If you don’t know where your log is, you should
   be able to get that info from your host.
 *   Forum: [Hacks](https://wordpress.org/support/forum/plugins-and-hacks/hacks/)
   
   In reply to: [How To Set post_id For Custom Post Type](https://wordpress.org/support/topic/how-to-set-post_id-for-custom-post-type/)
 *  [webbtj](https://wordpress.org/support/users/webbtj/)
 * (@webbtj)
 * [13 years, 4 months ago](https://wordpress.org/support/topic/how-to-set-post_id-for-custom-post-type/#post-3448550)
 * Looks good to me!
 *   Forum: [Everything else WordPress](https://wordpress.org/support/forum/miscellaneous/)
   
   In reply to: [WordPress scalability??](https://wordpress.org/support/topic/wordpress-scalability/)
 *  [webbtj](https://wordpress.org/support/users/webbtj/)
 * (@webbtj)
 * [13 years, 4 months ago](https://wordpress.org/support/topic/wordpress-scalability/#post-3448188)
 * If you’re adding 1000s a month without removing old ones then at some point you’re
   going to run into issues. But this is less of a WordPress issue and more of a
   database issue. SQL databases (including MySQL which WordPress uses) are not 
   infinitely scalable. Keep in mind it’s not like you’ll run into trouble any time
   soon, but if you’re eventually going to end up with a quarter million products
   or more, you may want to invest some of your revenue into a more scalable system.
   That being said I’ve seen MySQL databases with millions of records.
 *   Forum: [Everything else WordPress](https://wordpress.org/support/forum/miscellaneous/)
   
   In reply to: [Internal Server Error (Help! I have no technical experience,)](https://wordpress.org/support/topic/internal-server-error-help-i-have-no-technical-experience/)
 *  [webbtj](https://wordpress.org/support/users/webbtj/)
 * (@webbtj)
 * [13 years, 4 months ago](https://wordpress.org/support/topic/internal-server-error-help-i-have-no-technical-experience/#post-3448549)
 * Are you able to log into the back end of your WordPress site (yourdomain.com/
   wp-admin)? If so, try deactivating your plugins, if that still doesn’t work, 
   try switching to the “Twenty Eleven” theme, if that still doesn’t work your solutions
   will be to continue to grill GoDaddy or to hire someone technical to check out
   your error logs and find the source of the problem.
 * If your site was working fine, you changed nothing, and now it’s not working,
   the host would be the first place I checked, if there is a genuine PHP, Apache,
   MySQL error then they may have changed something, if the error now comes from
   PHP code and it wasn’t there before I would be concerned as to how the code was
   changed.
 * I won’t sway towards one host or another in a public forum, but GoDaddy is typically
   frowned upon by many, including a large chunk of the WP community.
 *   Forum: [Hacks](https://wordpress.org/support/forum/plugins-and-hacks/hacks/)
   
   In reply to: [How To Set post_id For Custom Post Type](https://wordpress.org/support/topic/how-to-set-post_id-for-custom-post-type/)
 *  [webbtj](https://wordpress.org/support/users/webbtj/)
 * (@webbtj)
 * [13 years, 4 months ago](https://wordpress.org/support/topic/how-to-set-post_id-for-custom-post-type/#post-3448546)
 * Are you creating the post first? If you can create the post with `wp_insert_post`
   it will return the ID of the new post (assuming there were no errors). [http://codex.wordpress.org/Function_Reference/wp_insert_post](http://codex.wordpress.org/Function_Reference/wp_insert_post)
 *   Forum: [Hacks](https://wordpress.org/support/forum/plugins-and-hacks/hacks/)
   
   In reply to: [Localhost Works Fine but Live Site Generating Header Error](https://wordpress.org/support/topic/localhost-works-fine-but-live-site-generating-header-error/)
 *  [webbtj](https://wordpress.org/support/users/webbtj/)
 * (@webbtj)
 * [13 years, 4 months ago](https://wordpress.org/support/topic/localhost-works-fine-but-live-site-generating-header-error/#post-3446986)
 * I would still try disabling errors on your live copy. You’re right that the first
   two are “just notices” that don’t really “stop” anything. The third, which is
   fatal, actually happens because the server is allowed to write out these errors,
   so it is printing errors to the browser screen, which is fine, but then later
   WordPress is trying to write header information, which cannot be done because
   stuff has already been written to the document (once document writing starts 
   you cannot write header information).
 * If you’re OK with coding and modifying the plugin you could wrap the two `if`
   conditions that are causing the notices in additional `if` conditions to test
   that $post is an object. It may also be as simple as running `setup_post($post);`
   before the $post object is used, I’m not too familiar with this plugin.
 *   Forum: [Hacks](https://wordpress.org/support/forum/plugins-and-hacks/hacks/)
   
   In reply to: [Localhost Works Fine but Live Site Generating Header Error](https://wordpress.org/support/topic/localhost-works-fine-but-live-site-generating-header-error/)
 *  [webbtj](https://wordpress.org/support/users/webbtj/)
 * (@webbtj)
 * [13 years, 4 months ago](https://wordpress.org/support/topic/localhost-works-fine-but-live-site-generating-header-error/#post-3446977)
 * Well the notices are happening because WP Access Control is trying to access 
   properties of something that isn’t actually an object. Based on line numbers 
   and assuming you’re running the current version of WP Access Control, it’s trying
   to get the ID property of the $post object, except it seems that $post is not
   actually an object, which seems odd since it is using the global $post object.
 * If everything is running fine on your local machine, I would assume that this
   is a small bug or plugin conflict. My educated guess would be that your local
   server just isn’t reporting warnings and notices to the screen. If you are getting
   the desired results and a looking for a quick solution, you can try this:
 * First confirm that the notices are actually triggered on you local copy. Add 
   the following code to the top of your `functions.php` file, inside of `<?php`
   tags: `error_reporting( E_ERROR | E_WARNING | E_PARSE | E_NOTICE);`. If you are
   now seeing these warnings on your local copy then the difference is the error
   reporting. If this is the case you can delete that line and check with your host
   about turning off PHP notices. You could turn them off yourself by adding `ini_set('
   display_errors', 'strerr');`. Ideally, you’ll have your host change the error
   setting on a higher level, but if they can’t help you this should work.
 * Ideally you would do some debugging with the `error_reporting` function above
   and see if there is a plugin conflict. If this problem occurs with all other 
   plugins disabled I would put in a support ticket with the developer of WordPress
   Access Control.
 * Good luck! Respond if you need any help
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Surveys] embed in a page](https://wordpress.org/support/topic/embed-in-a-page/)
 *  [webbtj](https://wordpress.org/support/users/webbtj/)
 * (@webbtj)
 * [13 years, 4 months ago](https://wordpress.org/support/topic/embed-in-a-page/#post-3374799)
 * When embedding on a page, does it just print out the “quick code” (example: [
   SURVEYS 1]) or is there nothing there at all? If the quick code is being printed
   out then your issue is probably with your theme, if may not be properly applying
   filters on the page template which means that quick code does not get replaced
   with what the plugin should be outputting.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [Can you stop wp_login_form redirecting to wp-login on fail?](https://wordpress.org/support/topic/can-you-stop-wp_login_form-redirecting-to-wp-login-on-fail/)
 *  [webbtj](https://wordpress.org/support/users/webbtj/)
 * (@webbtj)
 * [15 years, 4 months ago](https://wordpress.org/support/topic/can-you-stop-wp_login_form-redirecting-to-wp-login-on-fail/#post-1668319)
 * You are right, never a good idea to mess around with the core.
 * I see what you’re looking to do as I am trying to do the same. The process I 
   am going to go with is to handle the login myself manually. There is a function
   called wp_signon, you pass it an array of arguments (username and password) and
   it returns a user object. My plan of action is to create the HTML form, submit
   it to my own process (could be handled by a plugin or a function in the theme)
   and use wp_signon to validate the login. I’ll then use is_wp_error (passing the
   user object) to determine if it passed or failed authentication. From there you
   can do whatever you want as far as handling failed logins (or good logins for
   that matter).
 * In short – lookup wp_signon and is_wp_error in the codex.
 * -TJ

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