Search Results for 'ftp'

Updates via WP panel don’t often work due to mixed permissions on folders, where apache/server owns some things, and the ftpuser/site owner “owns” other things. If WordPress was installed via hosting panel vs manually via FTP, this is a very common problem.

Best way to upload, install, update any theme typically is to do so manually via FTP. (Making sure you backup everything before doing updates, of course.)

You can often check “ownership” permissions via your hosting panel/file manager, as it will show who owns what.

Hope that helped.

• Remove this line from Wp-config file (define(‘WP_CACHE’, true) )

• Check .htaccess file and if you see any code added by w3 remove it

It is usually inserted in a # section above the #wordpress section

The htaccess file is what is used to manage permalinks, and special instructions to the web server.

Usually at
/root/.htaccss

hidden by default; you will need to either set your ftp to filter view and show hidden files; or use the file editor in your hosting panel.

So, there might be a section

# W3CACHE stuff #
blah blah blah
# END #3 CACHE #

(delete the above in .htaccess file …)

Don’t delete .htaccess file completely as that is how the permalinks are able to work.

Good idea to learn to set FTP software to make that visible so you can backup when you do site backups.

Read more: http://www.shoutmeloud.com/how-to-delete-uninstall-w3-total-cache-wordpress-plugin.html#ixzz2sJKE3Fpq
Under Creative Commons License: Attribution No Derivatives

Mehedi
you would, via FTP, or hosting/file manager, delete the folder created by W3 cache which has all the cached content in it. (See W3 help for what folders are created; they should be pretty obvious if you look at your site via FTP on regular basis.) e.g.
wp-content/cache

Replace files … simply re-upload all your theme files if you think they were over-written.

As far as I know, W3 doesn’t “change” the theme folders, only serves cached copies. So, in theory, you should not actually need to replace the files in
/wp-content/themes/Newsapaper/

HOWEVER … one item which W3 cache doesn’t fix on deactivation, is cleaning up all the folders it creates in /cache/ and it doesn’t remove the cache “on” line which you would have added in your

/root/wp-config.php

and/or .htaccess file

UPSHOT: if you’re still seeing “cached” copies of content (old versions); you need to disable the caching completely

1) turn off plugin AFTER you clear cache in the plugin
2) delete the /cache/ folder contents wherever it made them
3) check your .htaccess file to remove any “directives” put there by W3 cache
4) check your functions.php file to change cache to “off”

And this presumes you’re making backup copies of everything !

If you’re new to WP, the wonderful repository for wordpress plugins is found at:
http://wordpress.org/plugins/

WP super cache is here
http://wordpress.org/plugins/wp-super-cache/

AS EVER: make backups of all your files; images, folders; make backup of dbase from your host/phpmyadmin; make backup of data files from wp admin > tools > export.

TEST anything before committing to it. If something doesn’t work, go back to the one that works from your backups.

Caching apps are tricky to use, and should generally be used ONLY by advanced users.

All seems to go good so far, just sorting all the ads and stuff out

No problem! Post if it goes successfully! or not… =)

• This reply was modified 12 years by adgower.

Cheers adgower, am updating right now!

No just copy everything over, and overwrite with the newer files. For the social counter to work you need to delete the old plugin, and upload the new one via ftp.

This does work. Just login via FTP, navigate to plugins folder delete the social counter plugin folder and reupload new version from downloaded theme package.

Well, Google will give you a code when you go to verify, and then when you put the code in, they ask you to click to confirm your site once the code is on your site, so if you did it properly you obviously got it. If you look at your site source code now, it should show the verification code. This is why a lot of people just upload the file via FTP and then leave it in the http root of your site (I did this for some sites, put the code in Yoast for others) … either way works — arguably if it’s in the file in your root docs it may save some space in your pages — meaning, not sure it’s “necessary” to have the verification code actually “printed” in the head of every page of your site once you’re verified… you need only do it once …. sooo…. if you figured it out, awesome!!! Glad I could contribute a little bit. I have been helping out a little to give Radu and Marius more time to get next version done which I need to finish a site launch for Feb. and then move on to other stuff. 🙂

i think i figured it out.

for all who have the same issue and maybe @davistar -> so if you want to exclude X articles of the latest post:

go (via ftp) to /themes/newspaper/page-homepage-loop. there you have to edit line 130 to this:

query_posts(‘offset=4’);

in this case the first 4 articles would be excluded.

Hey!
I chose to use Amazon’s CloudFront since I already have Amazon account and they bill my card on file (I think December was $0.98). CloudFront works well, aside from this pesky issue with Font Awesome 4, which I’m getting same issue from boostrapCDN (free) — sometimes the icons won’t load in IE10/11 or Firefox (both on Windows) for no good reason.

Anywayyyyyy….. in my case I’m using S3+CloudFront since my brother’s company (in the educational software business) uses it, a lot of folks have been testing running WP sites virtually entirely in their cloud (!), and I’ve got a nice app called Cloudberry S3 Explorer which works as both bulk FTP, header settings for expirations, ACL/Public settings, and CloudFront invalidations. So, it was just kind of the best choice. Right now only loading CSS, JS, fonts, static images (logos, little things like BBB bug, etc.). Not yet using for WP.

Upshot … I think folks would likely spend the 30-cents vs free to “test” both for speed.

In my case I did test couple of things against CloudFlare and where I’m at there was couple of msec saved, so seemed worth it to just use Amazon since I know they’re not going to disappear, or get bought by Google and squashed or anything else with other cloud stuff might throw out there. I’m also inherently suspicious of anything “free” as that is no business model, and I need reliable here today, here tomorrow setup for our main business site. So, $1 a month to count on it, vs “free” and might be gone without warning. Was easy choice for me.

Haven’t yet done anything with the WP stuff as waiting for Newspaper “3” if it will have classic WP ‘header.php’ file where I can just point a bunch of the CSS/JS stuff at the CDN without hacking something that will then need re-hacking in 2 weeks.

I also did some research on some articles around and since I don’t need SSL off the cloud (after all I have my own damn server!), this was food for thought:
http://robin.userapp.io/post/66094840975/finding-the-right-cdn-for-our-startup-maxcdn

Best bet is to
First check your wp-config and htaccess to see if something got “munched” there.

1) make a backup of your dbase from phpmyadmin from hosting account
2) make backup of WP data from your wp admin panel if you can login; and backup your wp-config.php and .htaccess file if you use one for permalinks.
3) turn off all plugins
4) turn off the Newspaper theme; go back to default “twenty-something”
5) reinstall wordpress via FTP proper way; re-upload theme files via FTP
6) make sure site works with default theme
7) preview newspaper theme
8) activate theme; turn on only “required” plugins

It sounds like you have something broken unrelated to theme.
Also check your permission on whether the ftp owner or Apache ‘owns’ your content, as this can cause major headaches, and I’ve found having your WP install ‘owned’ by Apache/server just doesn’t work properly. This is something to check with your hosting provider, or via your hosting account site panel for the file viewer which will show “owner” for each folder in your root public folder.

Hope that helped. Often best to ‘clean house’ when you’re having problems you can’t trace back to any one thing.

• This reply was modified 12 years by simchris.

Note to all, we found it’s better to manually minify the main style.css file each update.

HERE IS HOW TO:

The easy way to minify your main style.css file, is to
1) in your theme folder, make a copy of the style.css file (rename style-bak.css or whatever)
2) take the style.css file and open in a text editor (NOT a word processor), like Notepad or TextPad on Windows, or similar.
3) copy and paste all the text from the file into a minifcation online tool like one of these:
– http://refresh-sf.com/yui/
– http://cssminifier.com/
4) copy the “minified” output into a new style.css file
5) upload via FTP to over-write the style.css file in your theme root

Now when you run PageSpeed Insights it won’t bug you anymore. I do this and works just fine.

r1kay
to clarify, mod_pagespeed is not a WordPress plugin, but is used at the server level and is being used by many “speed oriented” web hosting providers now, including many that specialize in WP hosting specifically (and larger folk like GoDaddy, etc.).

The easy way to minify your main style.css file, is to
1) in your theme folder, make a copy of the style.css file (rename style-bak.css or whatever)
2) take the style.css file and open in a text editor (NOT a word processor), like Notepad or TextPad on Windows, or similar.
3) copy and paste all the text from the file into a minifcation online tool like one of these:
– http://refresh-sf.com/yui/
– http://cssminifier.com/
4) copy the “minified” output into a new style.css file
5) upload via FTP to over-write the style.css file in your theme root

Now when you run PageSpeed Insights it won’t bug you anymore. I do this and works just fine.

If none of that is remotely possible for you to do, then don’t stress over it. You only gain maybe a point for doing this, along with a couple of other things. Image optimization is far more important, and limiting use of plugins which “dial out” from your site to load things on the page beyond your content (social media “counters” for instance – plain buttons load faster).

You likely haven’t seen mention of mod_pagespeed as you have not been looking through the “pinned” topic at top of forum on “Pagespeed” issues.

Note when minifying the css file, it will save 20% of the space, but it doesn’t speed anything up by 20% or improve rating by 20%. If it saves more than 20kb then it’s worth it. If it saves less than 20kb may not be worth the trouble.

ALSO: be aware each time you update theme you will need to re-compress the style sheet using one of the tools above.

Hope that helped.

@zeus
not sure this helps:
1) go to your WP admin, left side under Settings > General
2) on the ‘general’ page you can set your blog title (name) and short description
( Use this instead of Theme > customizer > tagline )

Sometimes this will not work from the theme customizer panel, due to ownership permissions of the site (e.g., if WP installed from hosting panel vs from FTP manually).

With YOAST SEO, you can “also” override, or add to that by going to, from WP admin, left side
SEO > Titles and Metas > Home Tab
here you can enter meta description and keywords (if you have keywords ‘on’ in Yoast).

Hope that helps.