I cannot find anywhere in manual nor in any CSS tutorial the solution for this minor problem.
It’s just too complex for me.
I develop this website, basics made in the demoFW5. The pages are dynamic, made possible by certain code-elements that pull info from the database. One of these code-elements generates a list with linksand has to be placed inside an inline MarkUp element in order to function in the page.
My problem:
I cannot style the links that get generated. They are now blue underlined, which I do not want. I tried the several methods which usual work , creating new styles with specific names, wrap the markup inside a HTML box with the linkstyle action, etc etc)
I know it’s possible to format these links, an exempel can be seen here: NameBright - Coming Soon (look to the right, where one can choose one’s language) They even put a nice flag there, not that i would want that, but still…
Can someone please explain to me what I need to do with Freeway to be able to control the looks of these links?
Here’s an example using the code you posted <http://anoptic.com/demo/atelier/index.html>. Recreate the styles shown in my example in FW (edit as needed) and they’ll target the code in your markup item. Note that I’m assuming the naming scheme of the styles in the example you posted is in fact the same. If the style names are different then edit my styles as needed to match the markup.
If you’re unsure how to create these in FW and want the example FW Pro file let me know and I’ll send it off-list.
Sorry to say that this does not work, or I do not get it.
When I create a new style with the name of ul.simpletranslator
Freeway just takes away the dot, and the style-name becomes ulsimpletranslator just like that.
I tried this before myself with a style named simple-translator (like on the working page I showed in my post, they have there: <ul class=“simple-translator”) but FW just takes away the underscore in the name. I’m really stuck here!
Sometime around 28/2/08 (at 02:05 -0500) atelier said:
When I create a new style with the name of ul.simpletranslator
Freeway just takes away the dot, and the style-name becomes
ulsimpletranslator just like that.
Try putting “ul” into the tag field and “simpletranslator” into the
name field. That should do the trick.
but the element in my page needs a class like this:
The page (=the HTML that has been made by by Freeway) gets, because of the way this dynamic system works, modified on the server. The software there creates quite a lot of code from just one piece of code in my Freewaypage.
That piece of code is {exp:translator:simple} and it becomes:
removing the " - " will break the code. Unless I hack the backside. But then if I download an update, I must go to that file again. And I must update other installations as well.
(thanks for sending me the file, very kind of you)
OK, then what about either adding the styles manually (with " - ") into the Head tag or putting just those mark-up styles into a separate stylesheet and linking to it from FW?
Todd
On Feb 28, 2008, at 9:42 AM, atelier wrote:
removing the " - " will break the code. Unless I hack the backside. But then if I download an update, I must go to that file again. And I must update other installations as well.
(thanks for sending me the file, very kind of you)
I would modify your server code to use an underscore or some other
divider, like InterCaps, because Freeway is being cautious for a reason.
Walter
On Feb 28, 2008, at 10:25 AM, atelier wrote:
Very ennoying that Freeway does not allow me to have a “-” in the
word. FW alters in the style-menu simple-translator —>
simpletranslator…!!
Just thinking, maybe the only solution to place the CSS manually in
the page?
Where should I do that? And how should it look like?
thanks…
(what is the reason of this green field in the preview in this
message?
There is quite a lot of trickery going on server-side to deduce when
you are trying to enter code. The formatter tries very hard to make a
nice-looking code block for you when you do that. If you want to be
explicit about it, make sure you enter at least four spaces before
each line of code you want to display. This will cause the following
to happen:
Your text will be broken into lines exactly how you type it
Indenting will just work
<special characters> will appear correctly, instead of being
stripped out as if they were a clumsy hacking attack
You get a nice box around the code example, which shows it off nicely.
If you have a really really really long line with no returns,
the text will scroll horizontally without breaking the page layout.
You could do either of those. Make your external stylesheet in
CSSEdit or similar, and then open the Page : HTML Markup dialog,
switch it to the Before /HEAD section and add the following:
If you are using a non-strict DOCTYPE, then remove the trailing slash
before the closing bracket above.
Use an FTP app to upload the new sheet into your server. Make sure
that you get the path correct, because links like this fail silently.
I would take a look at the code that Freeway publishes when it is set
to use external stylesheets. If you switch that on in the Document
Setup : Output tab, you’ll get a nice example of what you need. Then
just tuck your extra stylesheet into the same /css folder that
Freeway creates at the root of your site.
If you want to add the CSS inline, then follow the same instructions
above, but put:
<style type="text/css">
//your styles here
</style>
in the Markup dialog.
Walter
On Feb 28, 2008, at 10:51 AM, Todd wrote:
OK, then what about either adding the styles manually (with " - ")
into the Head tag or putting just those mark-up styles into a
separate stylesheet and linking to it from FW?
Todd
On Feb 28, 2008, at 9:42 AM, atelier wrote:
removing the " - " will break the code. Unless I hack the
backside. But then if I download an update, I must go to that
file again. And I must update other installations as well.
(thanks for sending me the file, very kind of you)
Because it might want to fool with them later using JavaScript, which
interprets the hyphen as a minus operator. That’s just a guess, I’ll
rely on other more connected heads to tell me if I’m guessing correctly.
Walter
On Feb 28, 2008, at 10:58 AM, Todd wrote:
This is something else I’ve wondered about. Why doesn’t FW allow
dividers in styles?
Todd
On Feb 28, 2008, at 9:54 AM, Walter Lee Davis wrote:
I would modify your server code to use an underscore or some other
divider, like InterCaps, because Freeway is being cautious for a
reason.
I’ll use the inline CSS, to make it easier to keep changing my pages.
(Another option would be asking the creator of this simple -translator to remover the " - " in the code. :~)
Thanks a lot, all of you for your reactions, a lot of questions were answered!
I’m glad you got it working; it usually helps to look at the problem in the proper context (FW file) though it would have been simple if FW allowed dividers ( - ) in styles. It’s funny how little things like this can really screw with something so simple like creating a style.
Todd
On Feb 28, 2008, at 11:30 AM, atelier wrote:
Sorry to have come to that thought so late…;~)
And I wanted to tell that I managed to get it working…
And thank you again for sending me the FW file, because I could see there what can be done with that Style menu.
It would be useful if there was SOME kind of safe character that could be
used as Separator - though I UseCapsLikeThis as next best thing.
regards
Brian
Walter Lee Davis said recently:
Because it might want to fool with them later using JavaScript, which
interprets the hyphen as a minus operator. That’s just a guess, I’ll
rely on other more connected heads to tell me if I’m guessing correctly.
Walter
On Feb 28, 2008, at 10:58 AM, Todd wrote:
This is something else I’ve wondered about. Why doesn’t FW allow
dividers in styles?
Todd
On Feb 28, 2008, at 9:54 AM, Walter Lee Davis wrote:
I would modify your server code to use an underscore or some other
divider, like InterCaps, because Freeway is being cautious for a
reason.
I do hope some code-expert can help me out with this one too.
I tried to validate the page, and it seems that the output is not correct.
This is the error:
Line 142, Column 34: document type does not allow element “ul” here; missing one of “object”, “applet”, “map”, “iframe”, “button”, “ins”, “del” start-tag.
(and please be gentle with me, this is just a testpage…
As I explained above, I must accept the output of the element, because it gets generated by the server. Is there a way in FW to avoid this error? Must I add something in the CSS in the page-markup?
(I tried of course to embed the code-element in the page itself but that gives other problems. Cannot do that.)
Sorry to bother you with something that might be totally irrelevant for most of the FW users…
Somehow, you have an unordered list (bulleted list) inside a
paragraph. Did you do this directly in Freeway, or did you use a
markup item or another hand-coding trick?
Walter
On Mar 1, 2008, at 4:56 AM, atelier wrote:
I do hope some code-expert can help me out with this one too.
I tried to validate the page, and it seems that the output is not
correct.
This is the error:
Line 142, Column 34: document type does not allow element “ul”
here; missing one of “object”, “applet”, “map”, “iframe”, “button”,
“ins”, “del” start-tag.
I did not do the list myself in Freeway, the list gets generated after I publish and put things on the server.
It’s not easy for my to explain what happens here, because I do not “speak the code language” I can only explain it like I understand it myself…;~(
In short:
I have in my FW page an inline MarkUp element. This Element is just one word, it’s a piece of code. That piece of code calls from the server the list that you see in the HTML.
I had an issue with styles, I got a lot of help here, so I use this extra piece of CSS information in the Page MarkUp and my style problem is gone. That was great.
But now I see that the page does not get validated (one error), and I think that it’s is important to have things right.
I noticed that another page -using the same code- NameBright - Coming Soon also does not get validated, and for the same reason (as you see there are some more errors…) So I wrote the author of the plugin about this. Maybe he’ll fix this in an update? You can see my post here: Forums | ExpressionEngine
But in the meanwhile I asked my question here as well, hoping for a FW solution.
