mowse.ink

Thank you so much. I got the 500 error resolved with the host, and now the admin screen is loading as expected. Thanks for your help!

Thank you, @jarnovos for pointing that out … I will look into it right away.

@rogierlankhorst … Am I correct in thinking that Site Address (URL) in General Settings should be set to https?

This loaded in Chrome after sitting for quite a while:

View post on imgur.com

FYI: I left the admin panel page up for a while in Chrome, and this finally loaded, but when I refreshed, it doesn’t load again.

View post on imgur.com

This also appears sometimes after it sits for a while:

View post on imgur.com

• This reply was modified 1 year, 1 month ago by mowse.ink.

More info that I’m trying to make sense of:

This site was migrated from Media Temple to GoDaddy. I wasn’t the one who installed RSSSL on this site. The WordPress admin area is running on https. (I see the valid certificate when I click the padlock.) But the front end of the site is running on http. And the Site Address (URL) in General settings is still set to http. Could that be part of the problem? Should I change it to https?

UPDATE: In Chrome, the front end of the site is https (and says it’s protected), but in Safari it’s not.

• This reply was modified 1 year, 1 month ago by mowse.ink.

I resolved the error I posted above, which I determined was related to Advanced Custom Fields.

Even with a default theme activated (and all other plugins off), the admin panel loads as it does in the screenshot above.

I thought it was strange that even the RSSSL logo wasn’t loading, and I discovered an .htaccess file in the wp-content folder with this code:

# PROTECT wp-content
Order deny,allow
    Deny from all
    <Files ~ ".(xml|css|jpe?g|png|gif|js)$">
    Allow from all
    </Files>

When I renamed it (so it isn’t active), the RSSSL logo loaded — but none of the other panes are loading, and the Settings tab link doesn’t do anything.

Does that offer any clues?

Thank you for your quick reply, Rogier. We don’t use the Pro version.

Here’s the error:

Fatal error: Uncaught Error: Call to undefined function get_field() in /var/www/vhosts/oscilloscope.net/httpdocs/oscillo-WP-main1/wp-content/themes/oscope2/template-home.php:20 Stack trace: #0 /var/www/vhosts/oscilloscope.net/httpdocs/oscillo-WP-main1/wp-includes/template-loader.php(106): include() #1 /var/www/vhosts/oscilloscope.net/httpdocs/oscillo-WP-main1/wp-blog-header.php(19): require_once('...') #2 /var/www/vhosts/oscilloscope.net/httpdocs/index.php(17): require('...') #3 {main} thrown in /var/www/vhosts/oscilloscope.net/httpdocs/oscillo-WP-main1/wp-content/themes/oscope2/template-home.php on line 20

…but that error persists whether the Really Simple SSL plugin is activated or not. What’s odd is that when it’s activated, the homepage displays a critical error page:

View post on imgur.com

When it’s turned off, here’s what appears on the homepage:

View post on imgur.com

…and here’s what I see for the admin panel:

View post on imgur.com

I’d so appreciate any thoughts you’d have.

Thank you…
Jonathan

• This reply was modified 1 year, 1 month ago by mowse.ink.

Thanks, Tevye!

I was hoping to find some help with why the description limit doesn’t work. It truncates descriptions no matter how large a word limit is used.

Would you mind sharing what you switched to and if you’re happy with it? I love how many customizable features this has, but it’s clearly been abandoned.

Any fix for this? I can’t find info for all shortcode options.

• This reply was modified 7 years, 11 months ago by mowse.ink.

Thank you!! ?? j

Hi, Ryan…I got it all worked out. Seems it was due to the installation being on a temporary url for the staging site. Thanks! —jonathan

Hi, CosmetiCage…

Are you also using GoDaddy Managed WordPress?

I found this page about Jetpack that may explain what’s going on for me. My site is a staging site with a temporary url, so I think that may be the problem. And I had it working but disabled it, which I think is the problem:

Jetpack communicates with WordPress.com through a shared token and blog ID that is stored in the database. When the staging site is copied from the live site, these database values are included. Whenever you deactivate Jetpack, Jetpack communicates with WordPress.com to invalidate the token as a solid security practice.

For you, this means if you deactivate/disconnect Jetpack on the staging site, the same token used on the live site is now invalid. If this happens, simply have the client disconnect and reconnect Jetpack on the live site.

I may have to wait until we make the site live on the domain before I’m able to get it working again.

Thanks so much, Subharanjan, for the quick reply! That did it!! ??

Thank you, Dan, for your reply. Good luck to you.

This is a great plugin, though…If you find the time to update it, is there a way to find out?

Hello?…Anyone? Do I need to switch plugins?