David Burkhart
Forum Replies Created
-
Thank you for the kind update. The GitHub conversation makes it sound as if the “audio” shortcode will be dropped. Although, that would fix the error, I doubt that is what is meant by it.
Miss Bigelow: Photon does appear to more appropriately re-compress images only as needed. I am so used to optimizing them before uploading, that the other images had no need of further compression. So, that may explain why Photon left the other images alone.
Your theory about a non-conventional use of DOM sizes by Meta Slider seems like a great guess. The poor slider images do appear to be quite fuzzy, as if their resolution were reduced and then increased before having the resulting pixelation smoothed over. However, artifacts created around heavily contrasted areas of each image suggest over-compression contributed. Still, given the theory of side effects from improper size techniques, Meta Slider could be tripping over itself and re-compressing the images all on its own.
Given that Jetpack is worlds more valuable than any particular slider plugin, it’s no guess as to which plugin I have decided to do without – at least until the apparent conflict is resolved.
Miss Bigelow: Are you sure? The feature overview only mentions an alternative source for serving the images – nothing about compression. And, no, I don’t need to serve large or lossless quality images. I’m just looking to tweak overall website speed, but without website images becoming so unacceptably ugly.
After a little testing, the problem appears to be an incompatibility between Photon and a plugin, Meta Slider. Whenever I activate Photon, only the images within the slider become over-compressed. The rest of the images on the site look untouched.
I went further in my testing to compare original images to those that were being served through Photon (at least the ones that did not look over-compressed). They are not being compressed at all. This finding seems a bit more consistent with Photon’s overview which has no mention of compression.
Yes, the plugin patch still works. The modified version of WordPress 2.7, which I presume to have an integrated patch, did not work.
I tried the modified version of 2.7 you posted with your disabler plugin deactivated. The problem still occured. However, after upgrading Jetpack to 2.8, your disabler plugin still fixes or hides the problem.
Mr. Herve,
I am able to see a graphic for a zip file at that address. But, the link for downloading it does nothing. Permissions problem perhaps?
Mr. Herve,
Sorry for the delay. That one-liner plugin did the trick.
Thank you.
Any chance that I soon will no longer need your plugin? Or, am I going to need to hang onto this for a while?
It did help to refocus my testing.
The site I am using for testing uses a custom front page built into its theme. When I first saw that the front page was replaced with posts by Jetpack’s mobile theme, I immediately investigated Jetpack’s configuration settings for it. And, when I saw only a choice between showing excerpts or full posts on the front page, it seemed I had no other choice.
So, the problem turns out to be incompatibility between this plugin feature and the site theme’s built-in front page. Fortunately, the site’s theme provides a setting to disable the built-in front page.
Thank you for your suggestion, which did help lead me to find a work-around.
To fulfill such a simple need, it will be much easier for you to put the code directly into the page-content. I know, I know… everyone says it’s bad practice. But, proper protocol is simply not always practical either.
To eliminate the spacial overage in each table, start by setting the table width to “auto”. Then, set the cell spacing and padding for the entire table to zero and stepping either one up until you are happy with it.
<table width="auto" cellspacing="0" cellpadding="0"> <tr><td>Sunday: </td><td>Closed</td></tr> <tr><td>Monday: </td><td>9am - 5pm</td></tr> <tr><td>Tuesday: </td><td>9am - 5pm</td></tr> <tr><td>Wednesday: </td><td>9am - 5pm</td></tr> <tr><td>Thursday: </td><td>9am - 5pm</td></tr> <tr><td>Friday: </td><td>9am - 6pm</td></tr> <tr><td>Saturday: </td><td>Closed</td></tr> </table>Forum: Themes and Templates
In reply to: [Responsive] Logo Image on Top of Header ImageThat example is an extremely well-thought-out layout custom design. So, it’s good you were only interested in the logo part of it. The rest of that snazzy flexibility is way too much effort for this theme. If you can duplicate that functionality, you should be designing your own theme and demanding serious cash. But, I digress.
If you can find where the header image is specified (the <img> tag) in the code, add this line after it:
<img src="/myLogoPath/myLogoFile.png" alt="Logo" style="position:absolute;left:0px;top:0px;width:33%;min-width:200px;min-height:150px;">In theory this should give you a logo on top of the header, which starts out at a full size of 320 pixels wide and will shrink with the header image until 200 pixels wide. Of course, this is an over-simplified example of a solution. You will have to tweak the code to meet your particular circumstances. One possible complication with my example I see already is if the browser width ever causes the header image to drop below the minimum width or height of the logo, then the logo will overlap the navigation menu or vice versa.
Forum: Themes and Templates
In reply to: [Responsive] Header logoA much simpler solution would be to recreate your header image with a width of 960 pixels.
Forum: Themes and Templates
In reply to: [Responsive] Blue button code not workingI don’t know anything about the particulars of cross-browser hacks for background-image, but it seems to me by looking at your code that this should do the trick:
a.blue { background-color: #606788; background-image: -webkit-gradient(linear, left top, left bottom, from(#6B7398), to(#606788)); background-image: -webkit-linear-gradient(top, #6B7398, #606788); background-image: -moz-linear-gradient(top, #6B7398, #606788); background-image: -ms-linear-gradient(top, #6B7398, #606788); background-image: -o-linear-gradient(top, #6B7398, #606788); background-image: linear-gradient(top, #6B7398, #606788); border: 1px solid #555C79; color: #FFFFFF; filter: progid:DXImageTransform.Microsoft.gradient(startColorstr=#6B7398, endColorstr=#606788); text-shadow: 0 -1px 0 #555C79; } a.blue:hover { background-color: #888fac; background-image: -webkit-gradient(linear, left top, left bottom, from(#888fac), to(#606788)); background-image: -webkit-linear-gradient(top, #888fac, #606788); background-image: -moz-linear-gradient(top, #888fac, #606788); background-image: -ms-linear-gradient(top, #888fac, #606788); background-image: -o-linear-gradient(top, #888fac, #606788); background-image: linear-gradient(top, #888fac, #606788); border: 1px solid #115290; color: #ffffff; filter: progid:DXImageTransform.Microsoft.gradient(startColorstr=#888fac, endColorstr=#606788); text-shadow: 0 -1px 0 #555C79; }Forum: Themes and Templates
In reply to: [Responsive] Customizing HomepageMichaelo9,
Yajyolid is correct. If you want your title and/or tagline on every page, then it should probably be part of your header image.
The theme’s “custom” front page settings does offer the right half of the ugly white box as a container for an image. But, if you want any flexibility with the boring layout, you’ll need to first disable the theme’s home page override, “Appearance” > “Theme Options” > “Home Page” > “Enable Custom Front Page”. Then, change “Setting” > “Reading” > “Front page displays” to a static page of your choice.
Forum: Reviews
In reply to: [Responsive] Great theme to try out – a must-seeAll I did was take out the wordy detail about the header image. It was completely out of place, as you (Emil) yourself pointed out. Isn’t that why you posted the initial comment?
I don’t mean to frustrate you (Emil). I did not post my review looking for support. But, since you brought up some objections to my review, I merely addressed your concerns. And, since most people will never read these comments, I corrected the review concerning the header image.
Again, if I do re-install this theme, I will test again and update the rating and review accordingly. But, if I can’t get this theme to work and since a rating of two stars indicates that the theme at least “works”, the rating will stay at one star.
Forum: Reviews
In reply to: [Responsive] Great theme to try out – a must-seeTwo stars would indicate that the theme “works”. As it is, as soon as I specify a header image, the home page loads blank. I’m just reporting what I find.
I will verify the blank home page problem doesn’t occur with a different theme. If it does, then my WordPress install is likely now corrupted. If not, then I will try installing the theme again. Regardless, I will update the review with my findings.