amitstreak

Problem was different wamp versions.

Oren – thanks a lot for the solution.

Jose – Thank you, I would love to see a permanent fix that wouldn’t force me to go inside the code.

Glad to hear about the update.

If I may, I’d like to suggest that the update will include some styling options for the texts, such as font size, text color, etc.

Perfect!

That did the job.

A small note: instead of remarking the function itself I remarked the call for the function cause I didn’t want to leave a call to a function that isn’t there. Nothing serious.

Hi,

I gave it the highest rating.

I would appreciate it though if you could check if the plugin installs with the latin character set by default instead of UTF8 as happened to me several times, and if so, it would be great if you could release an update that fixes that so I (and other Hebrew users) don’t have to fix that after each installation.

Anyway, thanks for your help and cheers on the great plugin.

Hi,

Problem solved.

Since I made a few tries of fixing this problem I created several sites.
So when I changed the CHARACTER SET to UTF-8 it was on a different site than the one I was checking.
So now it’s alright.

I do wonder, though, how come it was not UTF8 originally after a clean installation.

Hi,
In order to find what is the character set for this table I ran this code I found on the internet (sorry, I don’t know how to do it):

SELECT CCSA.character_set_name
FROM information_schema.TABLES T, information_schema.COLLATION_CHARACTER_SET_APPLICABILITY CCSA
WHERE CCSA.collation_name = T.table_collation
AND T.table_name = “wp_scroll_news”

and I got:
latin1
latin1
latin1

So I used this query:

ALTER TABLE wp_scroll_news CONVERT TO CHARACTER SET utf8;

Then I checked again and this time got:
latin1
latin1
UTF8

I also checked the table structure and this is the CHARACTER SET for all columns:

id
title utf8_general_ci
content utf8_general_ci
createdon
custom_link utf8_general_ci

Still getting question marks.
I restarted the server and tried writing new news.

Is there anything else I can do or check?

Thanks.

Hi,

I’m not sure I understand the question.

The full table name is wp_scroll_news.

Thanks.

Hi,

First, I should mention that my WP installation is on a local machine and is using WAMP.

I searched for the text ‘character_set_client’ through the entire WAMP directory and found it in 2 places:

1. mysql_system_tables.sql
code: ‘character_set_client char(32) collate utf8_bin’
2. fill_help_tables.sql
code: ‘character_set_client: latin1’

Do I need to change anything?
I should mention again that I see Hebrew everywhere else.

Thanks!

Hi,

I checked and the reading settings were already set to UTF-8.
I have also added the <meta…> line but with no effect.

But I think the problem is at a more basic level than the theme level because at the “Manage Scrolling News” option I write the news in Hebrew but after I save them they change into question marks, and this has nothing to do with the theme.

I have tried on both a regular English WP installation and on a Hebrew localized installation, both new, but same result.

If you managed to see Hebrew than there’s some difference between our systems.

Would it be too much to ask you to install a fresh site and see if you can still get Hebrew with your plugin?

Sure:

??? ????? ???? ??????.
????.

Thanks.

Cause then the theme would still show and I’d like to show an empty page or one that says “under construction” only.

But I used the plugin mentioned above and I love the fact that admins see the real site and can work on it while other visitors see what the admin wants them to see.

I was just wondering if it can be done without using a plugin.

Haven’t looked at plugins yet.
I’ve been hoping for a non-plugin solution.
But thanks for that.

Amazing.

Worked like a charm.
I wonder why they’d make the “wildcard” addition automatic.

Anyway, I planned on fighting this issue all night long and you solved it in a sec.
Thank you so much.

I really appreciate the help.

In cPanel->subdomains where I added * it automatically added this: Document Root: /public_html/wildcard.

Also, I added the name of the subdomain itself, for example “biz”, so in cPanel->subdomains what was added was /public_html/biz.

I did install the main site under public_html.
After setting up the network, I created a new site from the administration panel and WordPress automatically created the dir “biz” under public_html, and in this dir I put the second WP installation.

I can repeat the process and let you know what was the exact error message.

OK, it’s not “I’d love to hear your solution” anymore.

I understand now that the way I made it work is incorrect.

Can you explain how do I create a subdomain site under the same WP installation and DB?