ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Problems editing templates in Safari 3.0 on mac

June 22, 2007 7:12am

Subscribe [5]
  • #1 / Jun 22, 2007 7:12am

    Phoebe

    58 posts

    Safari is behaving very strangely and changing my code.  It seems to happen progressively, so the first edit might be fine, then it all goes horribly wrong.

    For example:
    & appears

    &{assign_variable:template_name="site"}

    Quote changed to a semi-colon at the end of this line

    {embed="{template_name}/banner;}

    Although previous embeds were unaffected

    Not sure what is going on but going back to Flock!

  • #2 / Jun 22, 2007 9:04am

    ZulloP

    9 posts

    I already uninstalled Safari 3 Beta as I had many problems with it on many different webpages. Sorry, I can’t help you with your issue but I can recommend downgrade to version 2.x

  • #3 / Jun 22, 2007 9:11am

    PXLated

    1800 posts

    Why suffer? Downgrade…I did.
    There are a lot of flaky little things in Sb3.

  • #4 / Jun 22, 2007 1:44pm

    Derek Jones

    7561 posts

    From what I have seen, this is a result of some Input Managers you have installed for Safari.  Check the locations:

    ~/Library/Input Managers/
    /Library/Input Managers/

    And remove any and all installed extensions.  You’ll need to restart Safari see the change.

    For what it’s worth, Safari is my primary browser and at this stage in beta, it’s not worth it IMO to move to Safari 3.  If you want to experience the goodies of the new WebKit, run WebKit nightlies in tandem with Safari 2.  There’s an Applescript out there called “OpenWebKit” which will disable your input managers when launching WebKit, so you don’t have to manually move them out of the Input Manager folders every time.

  • #5 / Jun 22, 2007 2:33pm

    AlanM

    74 posts

    Admittedly, I’m pretty ignorant about these things. So I downloaded the nightly webkit prompted by this post and all I got was another Safari browser. There’s a debugger too.  But I can’t figure out where the supposed Web Inspector is?... anyone?

  • #6 / Jun 22, 2007 2:40pm

    Derek Jones

    7561 posts

    Web Inspector is in your contextual (right click / ctrl+click) menu, but you have to enable it first in the plist.  Open terminal and paste the command:

    defaults write com.apple.Safari WebKitDeveloperExtras -bool true
  • #7 / Jun 22, 2007 2:49pm

    AlanM

    74 posts

    Who would’ve thunk it only took a right click. Heh. It’s right there for me to use even without entering the code in a terminal. Thanks.

  • #8 / Jun 22, 2007 2:54pm

    Derek Jones

    7561 posts

    The terminal bit is just from my notes when it was first released.  Not surprised that it’s included in the new WebKit already, as it’s gotten a super sweet overhaul.

  • #9 / Jun 22, 2007 2:54pm

    AlanM

    74 posts

    I have to say…if anyone hasn’t looked at this Web Inspector they’re missing something pretty darn cool.

  • #10 / Jun 22, 2007 2:55pm

    AlanM

    74 posts

    Yeah, it’s very thorough.

  • #11 / Jun 22, 2007 3:48pm

    Halogen

    74 posts

    I noticed similar issues with Safari 3.  Looks like I’ll have to downgrade myself and wait.

    😊

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases