-- I'm not sure this is "programming", but could not find a better category --
I developed two modules, but after putting the files on de prod-server (and cleared cache/logoff/logon) i see the modules listed in system->configuration->advanced->advanced, but that seems to be all.
(I expected an extra admin-menu and routing to dynamic pages.)
- double checked completeness of files.
- site uses "varnish", but owner strongly believes this is not the problem.
i have limited access to this site (admin key and ftp, no shell)
possible tip from github:
Could this be relevant?
Is this safe to do in a live site?
any suggestion is very welcome !
Solved! Go to Solution.
Hi @Wiebrand L
Have you checked that your module is enabled on the production site?
You might have developed the module on the windows environment and deployed on Linux environment. So also check for case sensitive Tag names as well as any hard coded urls.
Both modules are enabled (default scope // all sites)
Yes, I did develop on Windows an now running on Linux
I already checked hard coded url's (none)
Can you elaborate on "case sensitive Tag names" ?
What are typical differences between Windows and Linux ?
now looking into that
Hello Wiebrand L,
I have a suggestion:
In production server, it's enable Compiler Mode. In the past, I have a same problem like you. I run compiler again and my module works ok. You read here or Google about Compiler Mode Magento.
Hope this works for you.
From the server's administrator:
"not running in compiler-mode and do not want to"
windows/Linux was the problem
specific: see Magento naming convention: Classnames have one (1!) leading capital and not more
(i used capitals on all parts on Windows)