Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • in reply to: Dante Feature Request #52228
    scubadollar
    Member
    Post count: 4

    Super Search for Portfolio items PLEASE!!!! Is this being considered as an option? I am going to develop it for my site this week if not.

    Thanks

    in reply to: HTML Modules will not save with copy pasted text #46806
    scubadollar
    Member
    Post count: 4

    Hi Guys and Gals,

    Fair enough the problem was special characters but the real problem is this…

    If I place an html entity in the RAW HTML Module for example: ™ and then save it, it converts it to a character and then if I try and edit, it won’t save again because it was converted to an improperly encoded character. So in order to work with the RAW HTML modules I need to create an html file and make all my edits there and then copy paste the entire thing in to the Swift RAW HTML form to save it. If I make any edits directly in the editor it packs up and requires me to delete and rewrite the html entities.

    Possibly at minimum an error warning might make it nicer to work with? Encoding is a bitch I know but the standard wordpress wysiwyg is no where near as finicky as this HTML Module.

    in reply to: HTML Modules will not save with copy pasted text #45909
    scubadollar
    Member
    Post count: 4
    This reply has been marked as private.
    in reply to: HTML Modules will not save with copy pasted text #43873
    scubadollar
    Member
    Post count: 4

    Hi Tahir, thanks for the response.

    I have no extra plugins. Only difference from the standard is I chose not to include Woo commerce.

    As far as formatting, I thought that too so I removed all formatting from the code by saving it as plain text and also as html so I could see clearly that no formatting existed. I have tried copy pasting small amounts and it works a couple times then locks. I have to cancel the process to get out of the dialogue.

    I even tried removing all extra spaces and line breaks in the code with the same result.

    It is very finnicky and provides no warnings whatsoever.

    I have tried Chrome, Firefox, Opera, Safari and IE 11 and all react the same.

Viewing 4 posts - 1 through 4 (of 4 total)