Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Forum: Fixing WordPress
    In reply to: Blank Page

    Create a file called blank.html and put the following in it:

    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    <HTML>
     <HEAD>
      <TITLE>Blank Page</TITLE>
     </HEAD>
    
     <BODY>
      <H1>Blank Page</H1>
     </BODY>
    </HTML>

    Upload that to your web server in the directory where your files are served from then navigate to http://yourdomain.com/blank.html

    Unless I’m mistaken, this isn’t really a wordpress specific issue, this is Basic Web Development 101.

    Forum: Fixing WordPress
    In reply to: Blank Page

    Can’t you just create a link to a page that you define (html, php, whatever)? Do you want it to sit completely outside of WordPress or am I missing something?

    Thread Starter iperks

    (@iperks)

    Hi Tobias,

    All tables have names although I have 3 with a title of ‘a’ but I can’t delete them:
    Fatal error: Cannot use string offset as an array in /.../wp-content/plugins/wp-table-reloaded/views/view-edit.php on line 5

    Regards,
    Ian

    Thread Starter iperks

    (@iperks)

    Thanks for the update.

    You may well be correct regarding the corrupt table and now you mention it that does make sense. From my perspective, with hundreds of tables uploaded I can’t easily check for corruptions.

    It doesn’t appear to matter what the search criteria are, they always give out the warnings regardless of whether any of the returned posts contain a corrupt table or not. As well as getting the warnings at the top of the page I also get them in a “recent posts” section but only after a search is conducted.

    Regards,

    Ian

    Thread Starter iperks

    (@iperks)

    Actually they are warnings not errors but still:

    Warning: array_merge() [function.array-merge]: Argument #1 is not an array in /.../wp-content/plugins/wp-table-reloaded/controllers/controller-frontend.php on line 392
    Warning: Invalid argument supplied for foreach() in /.../wp-content/plugins/wp-table-reloaded/controllers/controller-frontend.php on line 393
    Warning: array_merge() [function.array-merge]: Argument #1 is not an array in /.../wp-content/plugins/wp-table-reloaded/controllers/controller-frontend.php on line 392
    Warning: Invalid argument supplied for foreach() in /.../wp-content/plugins/wp-table-reloaded/controllers/controller-frontend.php on line 393
    Warning: array_merge() [function.array-merge]: Argument #1 is not an array in /.../wp-content/plugins/wp-table-reloaded/controllers/controller-frontend.php on line 392
    Warning: Invalid argument supplied for foreach() in /.../wp-content/plugins/wp-table-reloaded/controllers/controller-frontend.php on line 393
    Warning: Invalid argument supplied for foreach() in /.../wp-content/plugins/wp-table-reloaded/controllers/controller-frontend.php on line 422
    Warning: Invalid argument supplied for foreach() in /.../wp-content/plugins/wp-table-reloaded/controllers/controller-frontend.php on line 422
    Warning: Invalid argument supplied for foreach() in /.../wp-content/plugins/wp-table-reloaded/controllers/controller-frontend.php on line 422

    For us they appear when you’re searching for content using the default WP search widget and not in the WP admin area or the post itself. I guess it would be a theme specific issue …

    Thread Starter iperks

    (@iperks)

    Also, I’ve spoken to my boss and we’ll be donating some more money to your plugin site along with our thanks for your help.

    Regards,

    Ian

    Thread Starter iperks

    (@iperks)

    Hi Tobias,

    Thanks for the prompt response – easily found the offending table and have removed it – the search is now working perfectly!

    Thanks for your help.

    Regards,

    Ian

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