Site crash | Call to a member function getURL() on a non-object

Permalink
I'm getting an: "An unexpected error occurred. Call to a member function getURL() on a non-object" (screenshot:http://screencast.com/t/oiAEsgbkf)...

This happened when I added a image block, <saved> then deleted same image block a few minutes later after publishing.

Thanks,
Mark

Update: For due diligence, I contacted the theme developer and got this response:
"The image block is a core concrete5 block and not controlled or related to the theme.

If this issue persists you should submit a bug report to concrete5 and or post in the public forums to see if anyone else has encountered a similar issue."


Here is my configuration:

# concrete5 Version
Core Version - 5.7.3.1
Version Installed - 5.7.3.1
Database Version - 20150109000000

# concrete5 Packages
Fruitful (1.2), Fundamental (2.0.3), Open Graph Tags Lite (2.0.2).

# concrete5 Overrides
languages/da_DK, languages/de_DE, languages/el_GR, languages/fi_FI, languages/fr_FR, languages/it_IT, languages/ja_JP, languages/nl_NL, languages/ru_RU, languages/sl_SI, languages/sv_SE, languages/tr_TR

# concrete5 Cache Settings
Block Cache - Off
Overrides Cache - Off
Full Page Caching - Off
Full Page Cache Lifetime - Every 3 minutes.

# Server Software
Apache

# Server API
cgi-fcgi

# PHP Version
5.3.28

# PHP Extensions
bz2, calendar, cgi-fcgi, Core, ctype, curl, date, dom, ereg, exif, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, imap, ionCube Loader, json, libxml, mbstring, mcrypt, mysql, mysqli, openssl, pcntl, pcre, PDO, pdo_mysql, pdo_sqlite, Phar, readline, Reflection, session, shmop, SimpleXML, sockets, SPL, sqlite3, standard, tokenizer, wddx, xml, xmlreader, xmlwriter, xsl, zip, zlib.

# PHP Settings
max_execution_time - 60
log_errors_max_len - 1024
max_file_uploads - 20
max_input_nesting_level - 64
max_input_time - 60
max_input_vars - 1000
memory_limit - 128M
post_max_size - 8M
safe_mode - Off
safe_mode_exec_dir - <i>no value</i>
safe_mode_gid - Off
safe_mode_include_dir - <i>no value</i>
sql.safe_mode - Off
upload_max_filesize - 128M
mysql.max_links - Unlimited
mysql.max_persistent - Unlimited
mysqli.max_links - Unlimited
mysqli.max_persistent - Unlimited
pcre.backtrack_limit - 1000000
pcre.recursion_limit - 100000
session.cache_limiter - <i>no value</i>
session.gc_maxlifetime - 1440
safe_mode_allowed_env_vars - PHP_
safe_mode_protected_env_vars - LD_LIBRARY_PATH

mstroz
View Replies:
WillemAnchor replied on at Permalink Reply
WillemAnchor
Did you clear the cache ?
mstroz replied on at Permalink Reply
mstroz
Hi Willem,

Thanks for the reply. Yep, cleared the cache a few times and just triple-checked it again.
WillemAnchor replied on at Permalink Reply
WillemAnchor
can you revert to the original page before deleting the block ?
../index.php/dashboard

I couldn't find a reported bug (so far).
mstroz replied on at Permalink Reply
mstroz
Good direction. At first it wouldn't let me access versioning.

I changed the theme and was able to roll it back. But when I changed the theme back I got the same error message again. Tried it twice.
exchangecore replied on at Permalink Reply
exchangecore
Do you have anything at index.php/dashboard/reports/logs ?
mstroz replied on at Permalink Reply
mstroz
I do.

The first Emergency appears at Jul 29, 2015, 8:58:40 PM by User: Guest.

Then the logs are full of: Exception Occurred: /var/www/vhosts/drmillermacon.com/httpdocs/packages/fundamental/blocks/fundamental_section/controller.php:154 Call to a member function getURL() on a non-object (1)
mstroz replied on at Permalink Reply
mstroz
mstroz replied on at Permalink Reply
mstroz
Also, I just rolled it back to the last save prior to Jul 29, 2015, 5:17:40 PM version and I'm still getting the "An unexpected error occurred" message
exchangecore replied on at Permalink Reply
exchangecore
The error you posted looks to be coming from the `fundamental` package you have installed. You should reach out to the developer who created the package and send them this error message and what you did to receive it.
mstroz replied on at Permalink Reply
mstroz
I contact them first.

Their reply:
"The image block is a core concrete5 block and not controlled or related to the theme.

If this issue persists you should submit a bug report to concrete5 and or post in the public forums to see if anyone else has encountered a similar issue."
mstroz replied on at Permalink Reply
mstroz
I've posted the URL of this discussion on the support ticket I had with them and asked if they could respond/join the discussion.
c5hub replied on at Permalink Reply
c5hub
We have responded to the original ticket. Thanks.