All,
I’ve used SiteOrigin CSS on one of my websites for the last few weeks and it works great … no problems.
I then installed and activated SiteOrigin CSS on two other websites and it doesn’t work on either one (all 3 websites are on the same server). Clicking on either of the 2 icons (visual or expand) doesn’t produce a visual representation of the home page. Consequently, you can’t click on any element to modify.
This issue has come up on other support threads and the suggestions mention disabling all other plug-in’s. I did this and the SiteOrigin CSS plugin still doesn’t work on either site.
Any other suggestions on how I can resolve this problem? I *really* do not want to use another visual CSS editor.
Thank you,
Mark
Hi Mark,
Would it be possible for you to create a temporary admin account on one of the affected for us so we can log in and take a look?
This is a private message.
Hi Alex,
Good morning! I just sent set you up as an administrator on the two (2) websites where the SiteOrigin CSS plugin is not working:
http://www.twoa-gc.org
http://www.icwoa.org
You should have already received an email from both websites.
The SiteOrigin CSS plugin in installed and activated on both sites (but not working).
Thank you … and good luck!
Mark
This is a private message.
Hi Mark,
Unfortunately, we haven’t received an email from either of your websites yet. Can you please recreate the accounts? You’ll receive notification when we receive an email from your website.
Hi Alex,
I just set up new administration accounts for you on these two websites:
http://www.twoa-gc.org (Username: Private Snippet)
http://www.icwoa.org (Username: Private Snippet)
Using this email address for both:
Private Snippet
Also, after doing so, I received an email confirmation that both accounts were, indeed, setup.
Thanks,
Mark
This is a private message.
This is a private message.
Hi Mark,
I just got an email from twoa-gc.org with account information. I was able to log in as a result of the link that email.
I tried the Visual/Expanded editor in SiteOrigin CSS and it’s working without issue for me on that site. Was this site working previously?
This is a private message.
Hi Mark.
I just received an email from icwoa.org also. I tried SiteOrigin CSS on that website and it worked there also.
To confirm, does this issue occur if you try using SiteOrigin on a different browser or different computer?
Maybe try using SiteOrigin using the account you created for me.
Hi Alex,
I just discovered the problem with both sites. The login page for both of my sites is secure (https) … but the sites themselves are not secure (all pages are http). Consequently, the URL that SiteOrigin CSS uses for the Visual/Expanded editor is secure (https) … but, again, the actual page(s) I need to view are not secure (http). As a result, nothing shows up in the Visual/Expanded editor.
My immediate solution is to change the WordPress login page URL to non-secure (http). This solves the problem … although, the WordPress program gives a stern warning about signing into the WordPress site(s) without security. My long term solution is to make these two sites secure (https).
I find this situation curious because I have always signed into all of my non-secure (http) WordPress sites using a secure connection (https). Doing so has never caused a problem with any other plugin or theme. I’d like to think that a long term solution for this issue (on your end) is to have SiteOrigin CSS plugin check the contents of the “WordPress Address (URL)” field and the “Site Address (URL)” fields on the General Settings page (to see if it is a secure or non-secure site). Knowing this, the SiteOrigin CSS plugin would then direct/adjust the Visual/Expanded editor accordingly (that is, present the subject page as http or https).
As a side note, I’ve seen very similar issues in other posts on this forum (not being able to see anything in the Visual/Expanded editor). The only solutions proposed in most cases is to 1) check to see if there are any conflicting plugin and/or 2) to clear out the cache. Maybe the resolution of this issue will help other SiteOrigin CSS users in the future.
In any case, Alex, thanks so much for your time in trying to resolve this issue.
Best regards,
Mark