Moderator
t-p
(@t-p)
Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your admin panel, try deactivating all plugins. If you don’t have access to your admin panel, try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.
If that does not resolve the issue, try switching to the default theme for your version of WordPress to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue.
If that does not resolve the issue, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your SFTP or FTP client to view invisible files.
If you weren’t able to resolve the issue by either resetting your plugins and theme or renaming your .htaccess file, we may be able to help, but we’ll need a more detailed error message. Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that time period. If you don’t have access to your server error log, ask your hosting provider to look for you.
Hi,
I’ve checked the serve logs and here is the output:
[Fri Jul 15 20:23:25.116756 2016] [:error] PHP Parse error: syntax error, unexpected end of file in /var/www/anglokom.com/public_html/wp-content/themes/xenia/format-standard.php on line 55, referer: http://anglokom.com/2016/03/10/just-in-time/
[Fri Jul 15 20:24:24.334840 2016] [:error] PHP Parse error: syntax error, unexpected end of file in /var/www/anglokom.com/public_html/wp-content/themes/xenia/format-standard.php on line 55
Here is the content of that file:
cat -n /var/www/anglokom.com/public_html/wp-content/themes/xenia/format-standard.php on line 55, referer: http://anglokom.com/
1 <?php
2 global $layout;
3
4 $permalink = get_permalink();
5 ?>
6
7 <?php if ($layout == ‘medium’) : ?>
8 <div class=”col-lg-5″>
9 <?php endif; ?>
10
11
12
13 <?php if ($layout == ‘medium’) : ?>
14 </div>
15 <div class=”col-lg-7″>
16 <?php endif; ?>
17
18 <div class=”cl-blog-naz”>
19 <div class=”cl-blog-type”><i class=”icon-pencil”></i></div>
20
21 <div class=”cl-blog-name”>
22 “><?php the_title(); ?>
23 </div >
24 <div class=”cl-blog-detail”>
25 <?php the_time(‘j F Y’); ?> – <?php the_tags( ‘Tags: ‘, ‘, ‘, ‘
‘ ); ?>
26
27 </div>
28 <?php
29 if(!is_single()) { ?>
30 <div class=”cl-blog-img”>
31 <?php the_post_thumbnail( array( null, null, ‘bfi_thumb’ => true ) ); ?>
32 </div>
33 <? } ?>
34
35 <?php if ( is_single() ) : ?>
36 <div class=”cl-blog-text”>
37 <?php the_content(); ?>
38 </div>
39
40 </div><!– cl-blog-naz –>
41 <?php else : ?>
42 <div class=”cl-blog-text”>
43 <?php echo get_the_excerpt(); ?>
44 </div>
45
46 </div><!– cl-blog-naz –>
47 <div style=”overflow: hidden; width: 100%;”>
48 <div class=”cl-blog-read”>“><?php _e(‘Read More’, THEME_SLUG); ?></div>
49 </div>
50 <div class=”cl-blog-line”></div>
51 <?php endif; ?>
52
53 <?php if ($layout == ‘medium’) : ?>
54 </div>
55 <?php endif; ?>
Moderator
t-p
(@t-p)
– Your “xenia” theme seems to be the error.
– Try repairing/replacing /wp-content/themes/xenia/format-standard.php file
– If that does not resolve the issue, since “xenia” is a commercial theme, we ask that you please go to their official support channel, so you can get support from the people who know it best.
Forum volunteers are also not given access to commercial products, so they would not know why it is not working properly. Other community members who may have faced your issue might be able to help you but your best bet is your product’s developer. Keep in mind we encourage you to use the official support venues, as it allows the developers to be aware of issues with their code and gives back to the community in a more robust way.
