Search Results for 'block'

Most of it should be, assuming you’re running Apache/Linux. Note that the nice formatting of my code got kind of whacked when they moved to the new forum template…. soo.. might not be super readible/legible.

Kind of multiple threads going in my old mega thread — so, perhaps useful to work ‘backwards’ ?

a) some basic wp-config cleanups (add direct paths, memory change, image compression)
aa) htaccess stuff for common time to live, file type, redirect xmlrpc queries, etc.
b) some basic functions.php stuff to clean needless stuff in header of WP pages, remove stuff like XMLRPC stuff, some security stuff; remove ‘?’ queries on stuff (versioning);
c) optimize style.css with minifcation; compress main .js file per Google tool
d) consider moving to web-safe font stack and not loading ANY google fonts; have to hack out section in the main them booster function file, then search/replace the ‘font-family’ elements in the style.css (easier prior to minification, obviously)
e) put custom CSS bottom of style.css vs theme panel

advanced stuff included – un-enqueueing the main style.css, loading in footer; after generating “critical CSS’ with the critical CSS generator online; putting above the fold CSS in header.php (only way to remove render blocking css) ** not needed if moving to http/2 platform.

Super advanced peeps might choose to use mod-pagespeed, https, php 7, and http/2.

So, basically.. kind of a “test your speed,” (with *no* ads running); then make some mods; then retest couple of times, etc., rinse repeat.

I’m no longer using Newspaper – moved to NewsMag 3x last year entirely. Not yet on 4x. But also using TagDiv’s WPION thing as a beta test. (actually re-rendering thumbs for one test of that right now in other browser tab!).

Soooooooo….. basic Apache stuff, and WP-config.php stuff, and common sense thing for functions.php that do specific things — all useful. Good to research WHAT things do before using them.

• This reply was modified 9 years by simchris.

Hello Catalin,

AWESOME! This is exactly what I wanted. Thank you!

I tried the code on my blog and on desktop it seems to work just fine … but when I checked the site on ipad mini (with 768×1024 view port) … and samsung galaxy tab 10 (with an 800×1024 view port) the ad (300x250px) scrolls down below the featured image (300×250 px). I was hoping that the featured image / ad block would be responsive.

Would it be possible for you to modify/add the code so that the layout remains responsive on other devices? I would REALLY appreciate it.

THANK YOU SO MUCH FOR ALL YOUR HELP!!

On iphone resoultion

Quick question: what’s the best way to limit the css to a specific page?
Or, using the css editor inside the TD composer already does that? Asking because I don’t really want all the td_block_x to be affected by a change.

Tell me please , is it possible to do so in the footer , that would be like in the screenshot , the block 1 remains on the left edge , 2 and 3 the unit was aligned in the center screenshot

thanks for the reply simion

can i ask whether the screenshots are taken from an emulator or an actual tablet, and if a tablet what os was it using?

i have tried it on two different android versions, and an older ios, from 10″ to 7″, all showing the mobile theme.

i actually turned all caching off. removed every plug in that was doing any ‘speed’ or ‘optimisation job on my website. not just for this, but in several areas of development there was a nagging doubt caching could be the problem. i even followed steps to check for cache left overs (and actually found w3 traces from ages ago before i moved to super on theme advice). having removed all of that, and being 100% cache free, i turned off cloudflare and purged everything.

so one thing i can be pretty sure of is cache is not behind the issue.

i have started turning one or two optimisation bits on again. cautiously, checking everything each time an option is flicked.

it has been a useful exercise. a few upgrade issues have resolved themselves, though that may be more to do with your recommendation of switching to php 5.6. than the absence of caching – but having caching out of the way for a development month still seems to make sense.

there are just two issues that remain, and have remained throughout, this tablet displaying mobile theme, and corruption caused by full width blocks (that one i can live with for now)

what is the methodology of the mobile theme in what it serves itself to? is it screen size, resolution, some trigger in the device that says ‘i am a tablet or i am a phone’? might help narrow it down if i can get some more examples.

The ‘Block 6’ is being used on the frontpage with Visual Composer. Four articles are shown in here. After I’ve published one article on my Chromebook, three of them had 25 words and one of them 40. In the article published on the Chromebook, sentences also break off like described in my previous message, without any code in de text editor to make sense out of it. The frontpage setup is fully setup according to your documentation and based on one of the installed demo’s.