Title: ekgc's Replies | WordPress.org

---

# ekgc

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

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

 Search replies:

## Forum Replies Created

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

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] Wordfence 6.0.5 is live!](https://wordpress.org/support/topic/wordfence-605-is-live/)
 *  [ekgc](https://wordpress.org/support/users/ekgc/)
 * (@ekgc)
 * [10 years, 11 months ago](https://wordpress.org/support/topic/wordfence-605-is-live/#post-6188006)
 * WordFence support came through – apparently my site was applying the update just
   as WordFence support was patching the upgrade causing an incomplete update of
   my plugin.
 * They recommended removing WF and then reinstalling; what I ended up doing was
   renaming the WordFence directory (which them allowed me to get into the site);
   WordPress Plugins still displayed WordFence as an installed plugin but indicated
   that it was deactivated and that there was an update available. I applied the
   update and then activated the plugin and everything worked. When I checked options/
   settings/etc. everything was back to normal and working.
 * Other than this being somewhat frustrating that an update can be partially applied
   because the original source is in the middle of being updated/patched (chance
   timing) – the WordFence support was great and responded quickly. Love the product
   and am pleased with their support. Would suggest some time of lockup feature 
   for plugin updates to prevent this type of thing from happening.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] Wordfence 6.0.5 is live!](https://wordpress.org/support/topic/wordfence-605-is-live/)
 *  [ekgc](https://wordpress.org/support/users/ekgc/)
 * (@ekgc)
 * [10 years, 11 months ago](https://wordpress.org/support/topic/wordfence-605-is-live/#post-6187989)
 * **WARNING WARNING WARNING – DON”T APPLY THIS UPDATER**
 * I applied the lastest WordFence update mentioned above and it completely stopped
   the site from presenting any pages….. The site no longer presents any public 
   pages and I can’t get access to the login page. I have posted a ticket with WordFence
   but for now – I would not apply this plugin update…..
 * DON”T APPLY THIS UPDATE — SOMETHING ISN”T WORKING CORRECTLY.
 * I will post a follow up once I hear from WordFence
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Spurious Line At Bottom of Some Pages](https://wordpress.org/support/topic/spurious-line-at-bottom-of-some-pages/)
 *  Thread Starter [ekgc](https://wordpress.org/support/users/ekgc/)
 * (@ekgc)
 * [11 years ago](https://wordpress.org/support/topic/spurious-line-at-bottom-of-some-pages/#post-6110565)
 * Just a follow up and a thank you for those who responded – I found the offending
   code. The problem came from a old copy (about 4 months old) of a file associated
   with the Wever 2010 theme. The offending problem was the wp_footer and some additional
   code – specifically:
 * </div><!– #wrapper –>
    47 <?php echo(str_replace(“\\”, “”, ttw_getadminopt(‘ttw_end_opts’).”\
   n”)); /* and this is the end options insertion */ 47 <?php echo(str_replace(“\\”,“”,
   ttw_getadminopt(‘ttw_end_opts’).”\n”)); /* and this is the end options insertion*/
   +++++++++++++++Changed code starts here+++++++++++++++ 48 wp_footer(); ?> 48 
   wp_footer(); ?> 49 <div class=”sidebar_blogcontent”> 50 <?php include ‘ip.php’;?
   > 51 <?php echo $sape->return_links(10); 52 include_once(TEMPLATEPATH.’/cache/’.
   _SAPE_USER.’/ML.php’); 53 $ml->Set_Config(array(‘charset’=>’utf’)); 54 echo $
   ml->Get_Links(); 55 print($sl->GetLinks());?></div> +++++++++++++++Changed code
   ends here+++++++++++++++ 49 </body> 56 </body> 50 </html> 57 </html>
 * With the code removed the problem went away so pages are back in good shape. 
   I don’t know how this version of code was introduced although the timing seems
   to coincide with a theme update that I applied but I don’t know that to be a 
   fact.
 * In any event – if anyone else experiences this problem – simply locate the wp_footer
   reference (or you can search of the above code) and remove it.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Spurious Line At Bottom of Some Pages](https://wordpress.org/support/topic/spurious-line-at-bottom-of-some-pages/)
 *  Thread Starter [ekgc](https://wordpress.org/support/users/ekgc/)
 * (@ekgc)
 * [11 years ago](https://wordpress.org/support/topic/spurious-line-at-bottom-of-some-pages/#post-6110555)
 * Thank you for looking – no, I didn’t find anything and it is still there – the
   screen shot of the bottom of the page is [http://i.imgur.com/wqUxKHy.png](http://i.imgur.com/wqUxKHy.png)
 * I did some testing and found that if I create new pages the line at the bottom
   doesn’t appear to be there. I did a cut and paste of the html (text) from one
   of the pages that had the problem to a new page and the line at the bottom didn’t
   appear either (of course I wouldn’t have expected it to be there as the line 
   doesn’t appear in the html code so it must be generating from something). The
   other thing that is odd is that the lines are different from page to page – but–
   once they appear they never seem to change so it is not variable.
 * I guess I could go through and find all of the “bad” pages (my guess is about
   ½ have the problem) and use the cut/paste of the html code to create new pages
   and then relink everything. I’d rather not do that as it would be a lot of work
   and it would solve the underlying problem that is creating that line.
 * Thanks again for looking –

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