I went to a WordPress Webinar on introducing modules to SEO my WordPress Blog. There were hundreds if not a large number of modules to improve one’s blog. After the online course, I decided to introduce the Google XML Sitemap module. The moderators showed that this module was useful for my blog. After the download (introduce), I was unable to get over into my “Dashboard”. My blog was down! It took numerous hours to put this blog up by means of GoDaddy the host of my site. I felt that on the off chance that I paid for my site through GoDaddy I would not have these issues. I called GoDaddy about this blunder message and they said it would cost $150.00 to fix my blog! Information costs when managing the obscure. Remember that this fix is for a facilitated site. This blog was to be the one that I could develop from. My arrangement was to set up numerous quality online journals to assist individuals with taking care of their issues. Possibly I should begin by taking care of an issue that I made.
Exclusive on fiverr by qube97
How am I going to fix this? Whom do I call? I began to look the “Notice: Cannot change header data – headers as of now sent”…error message on Google, who else. I read and read until my eyes started to hurt. Gradually, I began to become familiar with a smidgen about FTP (Files Transfer Protocol).
I tried different things with ftp. I discovered my way to the root catalog and concentrated all the documents searching for wp-content/modules/wp-greetbox/wp-greetbox.php:1812, on the grounds that the issue was in the last module that I downloaded. Getting to the root catalog expects you to place this into your program: “ftpmysite.com”- them the program gives you the root Directory. At that point you go to “see” (drop down menu) on your program and snap “Open FTP Site in Windows Explorer”. At that point login (your ID&PW) and you will discover the records to your WordPress blog. Since the blunder message had to do with the wp-content Directory, click it and go to the modules Directory. Locate the last module that caused the blunder message. Now you can open an organizer and duplicate this record to your my reports. Presently be cautious and erase the replicated record from your ftp document. You caused a duplicate on the off chance that you to pick an inappropriate document.know more angular.
Open up another window to check your blog to check whether it is alright, if not proceed to duplicate and erase each module. Furthermore, you could simply duplicate the module envelope, at that point erase it, and afterward check your blog.
This data is from a non-nerd who went through very nearly two days finding an answer for this blunder message. In synopsis:
- Break down the blunder message (reorder to Notepad or to Word)
- Research the blunder message
- Research some more
- Get to the root registry as clarified previously
- Search for wp-content Directory – search for modules
- Go to your program click on the drop down menu “View”
- Snap “Open FTP Site in Windows Explorer”
- Login
- There it is-the records to your WordPress blog (be cautious)
- Open up another organizer [MyComputer] under “MyDocuments”(name it FTP, on the off chance that you need)
- Presently limit the two windows so they are side to side
- You ought to have the option to move the record being referred to from the server (have) to your “MyDocuments. 13. Erase, with extraordinary consideration the last module from the server/have (you have made a duplicate don’t as well concern) 14. Check your blog to check whether everything is OK
- Rehash the above until your mistake message vanishes.
Note: If your WordPress Blog is facilitated by GoDaddy, you can likewise check your records in the HOSTING area of there site. In addition, simply call the GoDaddy help work area and request help.
Waheat 