[dekket]

Since my initial post, I have decided to drop FlexForm because of the incredibly long load times. Of course, this isn’t an issue solely with FlexForm – it’s an issue with a lot of purchased themes. Because of that, I decided to roll my own theme from scratch instead.

[dekket]

But, that’s not the case though… Setting defaults for featured image/video for instance, is not there.
The perfect solution would be to simply have different ‘Default’ panels for each type of page/post. So Page, Single Post, Blog posts (overview)/Archive Pages, Category pages, as well as any custom post types, etc.
I know it’s a pain because of how WordPress uses post types and what not, but still.

[dekket]

Ed, these are not fixed in v1.5…
Not as many perhaps, but still plenty of errors when trying to minify. I didn’t track them all this time though.

[dekket]

Oh ok, I see.

[dekket]

The above snippet stopped working in v.1.4.3…
Not sure why as I can’t see a problem with it. But I also tried adding the full relative directory, i.e. ./../flexform-child/language/ – still isn’t being read from that directory… I checked and the permissions should be fine.

[dekket]

In the latest update. v1.4.3 (yesterday?), you didn’t fix these issues. I’d think they would be simple fixes? 🙂

[dekket]

Or, you could include my .po & .mo files when I’m done with translating the Admin UI 🙂

[dekket]

It’s not possible to simply check both directories?

[dekket]

Change “Background Size” to ‘Cover’, not Auto.

Mind you, I don’t work for SwiftIdeas 🙂

[dekket]

You can grab images of the Apple products on http://www.apple.com/pr/. Look at their guidelines to see what you’re allowed to do. If it’s a picture of an Apple product, you’re always liable to their guidelines.

I don’t work for SwiftIdeas, mind you. 🙂

[dekket]

I have discovered the issue.

I believe someone had a few shots of Vodka and then decided to change things right in the trunk. And then forget about it 🙂

Look at line 630 in the includes/meta-boxes.php and you’ll see what I mean. Hint: There is no such item in the array. 🙂

I’ve fixed the errors on my end, but please do sort it for the next upgrade. Thx.

[dekket]

Ok so… I have now done a quite thorough investigation into all the syntax errors. Please see screenshot of the CodeKit output 🙂 I’ve included the exact issues in the screenshot. There’s also a screenshot of Coda’s error about Mixed Line endings. Not sure what that is, but perhaps you guys do.

Turns out that there is indeed hidden characters in the file that you simply can’t see. This became apparent on the last error when I used the arrow keys to move the cursor, and it got “stuck” in one instance. It’s clear that it moved one bit but with zero size. So something has screwed up in between computers/editors/whatever. I’m guessing this is a problem with how Coda on Mac interprets file encoding on files edited elsewhere.
I did however find the opacity issues that I couldn’t find before. Turns out there’s a space in between “alpha” and the beginning bracket “(“.
Here are the declarations (pasted exactly):

#top-bar-social > ul {
float: right;
margin-top: 3px;
margin-bottom: 0;
-moz-opacity: 0.5;
filter: alpha(opacity: 50);
opacity: 0.5;
}

.logo-fade #logo a:hover img {
-moz-opacity: 0.6;
filter: alpha(opacity: 60);
opacity: 0.6;
}

It’s now been minified again and all works as it should. I think… 🙂

[dekket]

I have now looked in the original files from Themeforest, and I can’t find it either. So strange, since I never touched the flexform/style.css, I just override the styles from the child theme whenever I need to.

I have a feeling that the automatic update did a number on the files.

I’m gonna manually replace all now and see what the results are.. 🙂

[dekket]

Cudos on the awesome support btw 🙂

[dekket]

It’s in the flexform/style.css. Search for ‘filter:alpha(opacity’ and it should be there 🙂

I’m sure I can find it when I’m back in the office, no access on the phone :/