Loading...
 
Skip to main content

Features / Usability


Aaaack! My tiki has gone blank!

Our tiki has been online for a few months with no problems and its use is gradually increasing by the 20-30 people in the department. But then yesterday morning things started going funny... first reported by a user who wanted to create a new blog, and the "create blog" page just had a header and nothing else. We have been running a few blogs with no problem until now, and the permissions are all set, etc. Other pages etc seemed ok. As I looked into things that might have changed like themes/display and group permissions, the situation deteriorated to the point that now every page is completely blank. No error messages, nothing, just blank.

From digging around these forums and FAQ's, it sounds similar to a well-understood problem of memory_limit. But the limit was already at 32M, and we went ahead and upped it to 64M, with no change. Other web services on the server seem to be running fine.

What to do next? Is there a way to identify a specific error that is occuring? Is memory_limit of 64 still not enough? Would a re-install possibly help (while still preserving all the content that I have been encouraging people to contribute)?

I'm still very much a newbie in this area of troubleshooting, so I gratefully appreciate any suggestions or assistance.

Any ideas?

One of my colleagues found this forum thread: http://tikiwiki.org/tiki-view_forum_thread.php?topics_offset=1&forumId=4&comments_parentId=12901Question

Which sounds like a similar problem. From what I can tell, he is going to try these suggestions from that thread today:
Do the followings:

1- Go to tiki/template_c directory and delete the 2-character-folder regarding to your language setting (for e.g. en)

2- Go to tiki/temp/cache and delete whatever you see there

3- Go to tiki/modules/cache and delte everything but index.php and README


I guess if that doesn't work, then we will be going down the re-install/upgrade path... unless someone has a better idea?

thanks,
Mark


Ok, deleting the cache stuff didn't do the trick. But now I have some error messages to report:

[client 149.59.178.195] PHP Fatal error: Smarty error: [in evaluated template line 7]: syntax error: 'if' statement requires arguments (Smarty_Compiler.class.php, line 1261) in /opt/tikiwiki-1.9.7/lib/smarty/libs/Smarty.class.php on line 1095, referer: http://anrlx014.s.com/tiki/tiki-blog_post.php?blogId=12Question

[client 149.59.178.195] PHP Warning: Compilation failed: repeated subpattern is too long at offset 15897 in /opt/tikiwiki-1.9.7/lib/smarty/libs/Smarty_Compiler.class.php on line 1254, referer: http://anrlx014.s.com/tiki/tiki-list_blogs.phpQuestion


I guess I am encouraged by seeing some actual error messages now, and that it looks somehow related to the blog feature where trouble was first spotted, but I don't have any idea how to proceed from here. Help??

Thanks,
Mark


If you want to try clearing your caches, rather than using the file manager to delete contents from the templates_c directory, you can just go to System Admin (tiki-admin_system.php) and click on the three "Empty" links. If that doesn't help, then I'd suggest updating your installation.

Since the problem seems to not involve a particular blog post or even just the blog feature now, and since you're running 1.9.7, which has security vulnerabilities, I would upgrade your Tiki installation to 1.9.8.3.

If your Tiki is public (not on a private intranet), you might also take a look in your browser at the page source of some pages to check for any sign that your site has been vandalized. There've been cases of a div of porn links being added to Tiki template or php files, which don't display visually due to negative margins but are seen by bots, etc.

-- Gary


Thanks for the reply, Gary.

The System Admin page is blank along with the rest of the wiki, so I think we're going to have to bite the bullet and upgrade.

This is on a private intranet, so I don't think external vandalism is a factor, but it is good to note.

I'll post a follow up here (and in the docs) if I ever find out what exactly happened and how to fix it. Hopefully the upgrade will just get things running again.

-Mark


After long last, we got upgraded to 1.9.9 on a new server and are back up and running. Hooray!