• Home
  • Get help
  • Ask a question
Last post 10 min ago
Posts last week 94
Average response time last week 34 min
All time posts 67856
All time tickets 10487
All time avg. posts per day 20

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.
Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!
All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#106 – 500 error View class not found [class, file

Posted in ‘sh404SEF’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Saturday, 18 April 2015 20:58 UTC
gijs007
Dear Sir/Madam,

I've just uninstalled mijosef and installed sh404 on my Joomla 3.4 website.

The sh404SEF: Control panel loads fine, but when I try to load the URL manager I get the following error:

View class not found [class, file]: sh404sefViewurls, C:\Program Files\Apache Software Foundation\Apache24\htdocs\site 2\administrator\components\com_sh404sef\views\urls\view.html.php

I get similar error messages when loading the other pages, except for Control Panel and Documentation.

How can I resolve this?

Best Regards,

Gijs xxxx
Saturday, 18 April 2015 21:43 UTC
gijs007
I've noticed that the issue is caused by the php opcache.

Can you tell me which file(s) need to be excluded from the opcache?
Monday, 20 April 2015 09:15 UTC
wb_weeblr
Hi

None.

That's how opcache works. If you update the code running on your server, you must clear the cache, otherwise you risk having the wrong files running together.
You should do that (clear the cache) after each update of anything on your site, whether Joomla or any extension.

How you do that is dependant on your server setup though. If you have ssh access, you can simply restart the PHP process.

Rgds
 
Monday, 20 April 2015 09:22 UTC
wb_weeblr
Side note: unrelated to the above, but if you haven't yet, it'd be wise to exclude Joomla! /cache, /logs and /tmp folder anyway.

Rgds
 
Monday, 20 April 2015 13:23 UTC
gijs007
Yes, but this error happens in the Administrator interface.
Perhaps it's an idea to add some code to the admin interface of sh404 so that it doesn't get cached.
Monday, 20 April 2015 16:52 UTC
wb_weeblr
Hi

Administrator or front end doesn't matter. If you update an extension, you should clear the cache, to avoid discrepancies within extensions files.

Rgds
 
Monday, 20 April 2015 16:55 UTC
gijs007
The thing is, I don't update the extension. This just happens when switching pages in sh404.. I need to disable opcaching so that I can access it..
Monday, 20 April 2015 19:17 UTC
wb_weeblr
OK, but did you clear the opcache content since you installed sh404SEF?

I thought you actually updated sh404SEF not installed it. I never had report of opcache being an issue so far, and of course, I have opcache enabled on weeblr.com.

Wonder if this may be related to having mijosef before?
Is it possible to get a full akeeba backup of your site? I'd like to install on my local machine so I can step through the code and see if this happens on another machine

Rgds
 
Monday, 20 April 2015 19:29 UTC
gijs007
Yes, I cleaned the Joomla cache and restarted PHP (which clears the opcode cache)

I can attach the site with an akeeba backup, but I think the backup will be larger than the maximum allowed filesize (which is 2MB) that I can add to this ticket ;)
Monday, 20 April 2015 19:36 UTC
wb_weeblr
Hi

No, you can't attach here. Usually, users put that on dropbox or similar with a download link, or you can use services such as wetransfer, or even simply provide super admin access to backend with a temprary user, so I can download it directly.

Rgds
 
Monday, 20 April 2015 19:42 UTC
gijs007
I've created an account for you:

login: xxxx
password: xxxx

at: https://www.xxxx.net/administrator/
Tuesday, 21 April 2015 11:20 UTC
wb_weeblr
Hi Gijs,

Sorry, I thought you would have already installed akeeba and done the backup. I was only mentioning superadmin access as a way to download. I can do it, but I need you explicit permission to install anything on your website.

Rgds
 
Tuesday, 21 April 2015 11:22 UTC
gijs007
Yes, you may install akeeba.
It might also be handy to have a look at the links you wanted to see (see ticket 108)
Wednesday, 22 April 2015 10:57 UTC
wb_weeblr
Hi

Installed backup, but can't reproduce the problem. My config is real close to yours, running apache and php on a windows machine.
Restored the site, loaded a few pages here and there, accessed sh404SEF backend (all pages), cheched that parts of sh404SEF were in opcache.
Installed sh404SEF version 4.4.6, went straight to URL manager, no problem
Installed again 4.4.9, same thing no problem.

Actually, I can access sh404SEF url manager and all other files without problem on your site also.

No clue

Rgds

 
Monday, 27 April 2015 18:38 UTC
gijs007
I only get the problem after switching from one sh404sef url page to another, for example first going in to the control panel and then into the URL manager.

I have a feeling it might be caused by my opcache settings, more specifically: opcache.use_cwd=0

Also try these opcache settings:
zend_extension="C:\Program Files (x86)\PHP\ext\php_opcache.dll"
; Determines if Zend OPCache is enabled
opcache.enable=1

; Determines if Zend OPCache is enabled for the CLI version of PHP
opcache.enable_cli=1

; The OPcache shared memory storage size.
opcache.memory_consumption=256

; The amount of memory for interned strings in Mbytes.
opcache.interned_strings_buffer=16

; The maximum number of keys (scripts) in the OPcache hash table.
; Only numbers between 200 and 100000 are allowed.
opcache.max_accelerated_files=50000

; The maximum percentage of "wasted" memory until a restart is scheduled.
;opcache.max_wasted_percentage=5

; When this directive is enabled, the OPcache appends the current working
; directory to the script key, thus eliminating possible collisions between
; files with the same name (basename). Disabling the directive improves
; performance, but may break existing applications.
opcache.use_cwd=0

; When disabled, you must reset the OPcache manually or restart the
; webserver for changes to the filesystem to take effect.
opcache.validate_timestamps=1

; How often (in seconds) to check file timestamps for changes to the shared
; memory storage allocation. ("1" means validate once per second, but only
; once per request. "0" means always validate)
opcache.revalidate_freq=60

; Enables or disables file search in include_path optimization
;opcache.revalidate_path=0

; If disabled, all PHPDoc comments are dropped from the code to reduce the
; size of the optimized code.
opcache.save_comments=0

; If disabled, PHPDoc comments are not loaded from SHM, so "Doc Comments"
; may be always stored (save_comments=1), but not loaded by applications
; that don't need them anyway.
opcache.load_comments=0

; If enabled, a fast shutdown sequence is used for the accelerated code
opcache.fast_shutdown=1

; Allow file existence override (file_exists, etc.) performance feature.
opcache.enable_file_override=1

; A bitmask, where each bit enables or disables the appropriate OPcache
; passes
opcache.optimization_level=0xffffffff

;opcache.inherited_hack=1
;opcache.dups_fix=0

; The location of the OPcache blacklist file (wildcards allowed).
; Each OPcache blacklist file is a text file that holds the names of files
; that should not be accelerated. The file format is to add each filename
; to a new line. The filename may be a full path or just a file prefix
; (i.e., /var/www/x blacklists all the files and directories in /var/www
; that start with 'x'). Line starting with a ; are ignored (comments).
;opcache.blacklist_filename=

; Allows exclusion of large files from being cached. By default all files
; are cached.
opcache.max_file_size=0

; Check the cache checksum each N requests.
; The default value of "0" means that the checks are disabled.
;opcache.consistency_checks=0

; How long to wait (in seconds) for a scheduled restart to begin if the cache
; is not being accessed.
;opcache.force_restart_timeout=180

; OPcache error_log file name. Empty string assumes "stderr".
;opcache.error_log=

; All OPcache errors go to the Web server log.
; By default, only fatal errors (level 0) or errors (level 1) are logged.
; You can also enable warnings (level 2), info messages (level 3) or
; debug messages (level 4).
;opcache.log_verbosity_level=1

; Preferred Shared Memory back-end. Leave empty and let the system decide.
;opcache.preferred_memory_model=

; Protect the shared memory from unexpected writing during script execution.
; Useful for internal debugging only.
;opcache.protect_memory=0
Monday, 27 April 2015 19:30 UTC
wb_weeblr
Hi
I only get the problem after switching from one sh404sef url page to another, for example first going in to the control panel and then into the URL manager.
Yes, like I said I've done that a number of times.
I have a feeling it might be caused by my opcache settings, more specifically: opcache.use_cwd=0
I'm not competent enough on the field, but that seems liek something risky if you have several sites with sames files name on the same server: https://github.com/zendtech/ZendOptimizerPlus/issues/94

Rgds
 
Monday, 27 April 2015 20:29 UTC
gijs007
It can also be a performance improvement, when both sites use the exact same software ;)
Tuesday, 28 April 2015 08:01 UTC
wb_weeblr
If you can measure the improvement, yes, why not. I very strongly doubt you can get any measurable perf improvement from that.
What you might get is a rather small saving in memory used (by not duplicating cached versions of files that would otherwise use the same cached version).
At weeblr.com, a rather heavy site with quite a few extensions, opcache barely uses 70MB of RAM - with a 99.97% hit rate. So this is the order of magnitude of the saving...

Rgds

 
Wednesday, 13 May 2015 05:34 UTC
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.