News:

Wondering if this will always be free?  See why free is better.

Main Menu

Error 2.1 rc 2 theme or forum?

Started by Schizophren1c, September 21, 2019, 05:16:06 PM

Previous topic - Next topic

Schizophren1c

Theme i am using is wide and is compatible for my version of forum which is 2.1rc

so the problem is when ever i try to modify any thread i get this type of error

shawnb61

At first glance, your content appears to be double-encoded. 

Is this a new, blank forum?  Does your content look OK when browsing the forum?

Or was your forum upgraded from 2.0.x?   

If it was 2.0.x, was it encoded to UTF8 before the upgrade to 2.1, or was it converted to UTF8 during the upgrade to 2.1?

Do you get similar issues using the forum's default theme, Curve2?

If you look at your content using a DB tool, such as phpmyadmin, does it look the same, with all the funky characters?
Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp

Schizophren1c

Quote from: shawnb61 on September 21, 2019, 05:39:39 PM
At first glance, your content appears to be double-encoded. 

Is this a new, blank forum?  Does your content look OK when browsing the forum?

Or was your forum upgraded from 2.0.x?   

If it was 2.0.x, was it encoded to UTF8 before the upgrade to 2.1, or was it converted to UTF8 during the upgrade to 2.1?

Do you get similar issues using the forum's default theme, Curve2?

If you look at your content using a DB tool, such as phpmyadmin, does it look the same, with all the funky characters?
forum was updated from 2.0 but i completely delete 2.0 before upgrading,  other themes are fine no issue, last check 1 month ago when forum was new .
db tool is fine i dont know much about that
forum is live n getting 500 unique visitors a day

shawnb61

This is easily reproducible if you install and use the Wide A Responsive Theme, even the proper RC2 version. 

The theme author needs to address this. 

And...  I see you have posted on that thread - perfect
Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp

RML

The problem is in the index.css file. Look for this:

.mvisible::before {
content:

and

.mvisible::after {
content:


and delete that many strange caracters ("ÃÆ'Įââ,¬â,,¢ÃƒÆ'ââ,) after them.


gecitli

Quote from: shawnb61 on September 22, 2019, 12:20:07 AM
This is easily reproducible if you install and use the Wide A Responsive Theme, even the proper RC2 version. 

The theme author needs to address this. 

And...  I see you have posted on that thread - perfect

This is not a problem with the theme, this problem is in the default theme, the same problem is the character problem

.mvisible::before {
content: "« ";
}
.mvisible::after {
content: " »";
}


This character is problematic
»
http://www.webtiryaki.com
webmaster forumu
Free & Premium Responsive Themes for SMF.

Arantor

Don't put raw Unicode in your CSS, ever, doubly so in 2.1. Use the \u syntax to embed it correctly.

Schizophren1c

Quote from: RML on September 22, 2019, 02:34:54 AM
The problem is in the index.css file. Look for this:

.mvisible::before {
content:

and

.mvisible::after {
content:


and delete that many strange caracters ("ÃÆ'Įââ,¬â,,¢ÃƒÆ'ââ,) after them.
man u are superb problem solved thank u so much

RML


shawnb61

@gecitli -

Following up on what RML posted...  This is what lines 3272-3276 look like for index.css in the distribution for Wide A:
.mvisible::before {
content: "ÃÆ'Įââ,¬â,,¢ÃƒÆ'ââ,¬Â ÃƒÂ¢Ã¢â€šÂ¬Ã¢â€žÂ¢ÃƒÆ'ƒâ€Ã, ÃÆ'Ã,¢Ã¢ââ,¬Å¡Ã,¬Ã¢ââ,¬Å¾Ã,¢ÃÆ'Įââ,¬â,,¢ÃƒÆ'Ã,¢Ã¢ââ,¬Å¡Ã,¬Ã‚Ã, ÃÆ'ƒÂÃ,¢ÃÆ'Ã,¢Ã¢â‚¬Ã...¡Ã‚Ã,¬ÃÆ'Ã,¢Ã¢â‚¬à ...";
}
.mvisible::after {
content: " ÃÆ'Įââ,¬â,,¢ÃƒÆ'ââ,¬Â ÃƒÂ¢Ã¢â€šÂ¬Ã¢â€žÂ¢ÃƒÆ'ƒâ€Ã, ÃÆ'Ã,¢Ã¢ââ,¬Å¡Ã,¬Ã¢ââ,¬Å¾Ã,¢ÃÆ'Įââ,¬â,,¢ÃƒÆ'Ã,¢Ã¢ââ,¬Å¡Ã,¬Ã‚Ã, ÃÆ'ƒÂÃ,¢ÃÆ'Ã,¢Ã¢â‚¬Ã...¡Ã‚Ã,¬ÃÆ'Ã,¢Ã¢â‚¬à ...";
}
Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp

Advertisement: