jordanwpcom

Hey @storefrontcity,

Ok that’s interesting, perhaps it is bundled with your theme.
The first file I’d check is footer.php within your theme folder.
Then I would check index.php, page.php and post.php also from within the theme folder.

If you find that chunk of code, delete it.

Let me know if you still can’t find it.

• This reply was modified 7 years, 9 months ago by jordanwpcom.

Hey @storefrontcity,

Sorry, I am not seeing my original reply.

It looks like there is a “:)” symbol underneath your footer in the left corner causing the extra space.

The code is:

<img src="https://pixel.wp.com/g.gif?v=ext&j=1%3A5.0&blog=87655099&post=7816&tz=0&srv=www.citizen-state.com&host=www.citizen-state.com&ref=http%3A%2F%2Fwww.citizen-state.com%2Faction%2F&rand=0.43693387186385313" alt=":)" width="6" height="5" id="wpstats"/>

Looks like wpstats may be the cause, do you have that plugin installed? Try deactivating it…

Hope that helps!

• This reply was modified 7 years, 9 months ago by jordanwpcom.
• This reply was modified 7 years, 9 months ago by jordanwpcom.
• This reply was modified 7 years, 9 months ago by jordanwpcom.

Hey @yelloq,

I am not entirely sure I fully understand your question…

What exactly are you trying to do??

Hey @qnkov,

It could very well be a plugin conflict. It could be a number of things!

Can you supply some links to your website so I can see the pagination errors?

Hey @catalinciubotariu,

To add to that…

The WordPress updater from within WordPress uses the same type of FTP connection you would need to manually upgrade using an FTP client, like Filezilla.
It is very likely that the upgrades from within WordPress are failing because WordPress does not have the correct FTP credentials set or the folder permissions are not setup correctly.

Unfortunately, the only way to make the upgrade is to contact the hosting provider and obtain the correct FTP host and login to move forward.

If after you get the proper FTP credentials you are still having issues, feel free to post a follow-up here ??

Hey @timaurus

Interesting enough, I opened your link, entered the password, and it took me directly to that post page. Everything seemed to work perfectly ??

Are you running into this issue while being logged in as admin in WordPress? Can you try logging out?

From my understanding…”A 401 Unauthorized error means the page you were trying to see needs valid user ID and password before you can view it.”
Any chance you were entering the password wrong?

• This reply was modified 7 years, 9 months ago by jordanwpcom.

Hey @ikohut,

I’d recommend deleting all WP files and cleaning out the database.
Then, download the newest version of WordPress and upload it.
Run the install again and you should be able to get through it.

If you have any further issues feel free to post it!

Hey @gregmini,

Sounds like you got things sorted, but for your future reference…

Before anything, you need to ensure the domain has been properly added to BlueHost. Take note of the “root” folder the domain is connected to, which is the folder WordPress needs to be installed in.
If that is in good order, you can use the 1-click WordPress install to set everything up.
In the 1-click install settings page, make sure WordPress is being installed to the EXACT same “root” folder that the domain is pointing to.
After the install, go to the file explorer, navigate to the “root” folder and see if the wp files are there.
If the files are in the “root” folder, when you go to your domain in a web browser, you should be WordPress.

You can use the same email address for as many WordPress installs you need. I’ve used the same email address for hundreds of sites!

Hope that helps ??
Feel free to ask more questions if you need.

Hey @sachin06,

Just wanted to add to this…

There are 2 types of WordPress updates, major and minor. A minor release (like 4.7.4 to 4.7.5) generally consists of patches and security updates, etc. These very rarely cause any issues when upgrading, and can even be set to automatically upgrade as you are not likely going to have any issues.
A major release (like 4.7 to 4.8) generally consist of big bug fixes, feature add-ons, layout changes, etc. Sometimes, these can be tricky to upgrade, and should be handled manually. For a major release, you should backup the WordPress website before the upgrade, run the upgrade on a staging version of your website, then analyze it from there.

Hope that helps ??

Hey @vanguian92,

As Steve mentioned, there is no way for anyone outside of your localhost to view the links you have posted, making this issue difficult to troubleshoot.
I also have to agree with Steve in his 2nd reply, those 3 links are not the WP Logo, so if those are missing, they shouldn’t impact the login page.

Can you upload to a web server and post the links?
Are you upgraded to the latest version of WordPress?

Hey @svigue,

JetPack has many great features, but if you disabled the plugin and find everything works better then you should just leave it disabled.
Sometimes certain plugins and certain themes conflict with each-other, this might be one of those cases…

• This reply was modified 7 years, 9 months ago by jordanwpcom.
• This reply was modified 7 years, 9 months ago by jordanwpcom.

Hey @angeladesign, sure, I’ll try and help you the best I can!
The screenshot you supplied doesn’t show the entire code.

It’s less about generating a link to the search page, and more about passing the tag link keywords through the WordPress search query, then generating the page and linking to it, all automatically.

How do you have those tags setup? If I’m reading the code correctly you’re using categories?
I can’t see any easy way of updating your current code to make this work, you may very well need to redo the entire section.

Or, a less dynamic solution could be to hard-code the links in each tag. So “Bright” links directly to – https://www.seacole.com/?s=Bright – but this would require you to enter the keyword in the search bar, copy the url, and create each link individually.

Hey Javier, haha, these things happen, no need to apologize! Browser cache get’s us all sometimes…

Great!
Glad that worked out, I had a feeling a fresh database would do the trick.

Hey @javiersivack,

Ok, so just based on what you are saying, I’d guess there is something misconfigured with the actual localhost. If you create a folder, and create a simple index.php file, when you view that index page in a browser you should definitely see the contents. If this isn’t the case, then WordPress will certainly not work.

Curious, how do you have this localhost setup?
Can you confirm everything is setup correctly?