tried to add modules to ftp server direct. then big bug error so deleted files so related.

now my website is blank ie no content?

modules i tried to add were..

supernav-6.x-1.0.tar.gz
module_builder-6.x-1.x-dev.tar.gz
journal-6.x-1.1.tar.gz
helpers-6.x-1.1.tar.gz
admin_menu-6.x-1.x-dev.tar.gz
themesettingsapi-6.x-1.4.tar.gz
statcounter-6.x-1.0.tar.gz

once the bug showd itself i deleted it and all ar & ap was to be reconciled and brought to account.
Hope this helps for now

please hep,

Kindest,

gigfish

CommentFileSizeAuthor
#18 Picture 2.png379.9 KBgigfish

Comments

gpk’s picture

gpk commented
Component: update system » base system
Category: bug » support
Priority: Critical » Normal

(Related posts at http://drupal.org/node/256114 and http://drupal.org/node/126098#comment-836257).

In your other posts you also mention four seasons module and devel so I'm not clear exactly where the problem has arisen.

Anyway, if you go into the {system} table in the database you can set the status for the suspect modules to 0 to disable them. May solve your problems.

Also have a look in the {watchdog} table and in your Apache error and access logs for any message that may give a clue as to the cause of the problem.

I'd suggest never experimenting with new modules on a live site - always use a "disposable" sandbox in order to avoid this problem (probably you've worked that out yourself now!). Some of the modules you have installed are "developmental" versions and therefore likely to be buggy.

gigfish’s picture

gigfish commented

i started with four seasons all was ok and running fine.

i downloaded a few modules... and added them .. site crashed.. then researched all modules and found and issues with devel.. no issues with others i dont think given m y quick research..

anyhow yes learnt the lesson the hardway - now to getting my site backup...

how do i get into the system and watchdog table im not familiar with these?
i just use ftp..

thanks

gpk’s picture

gpk commented

Your web hosting probably comes with an interface for manipulating your databases, e.g. phpMyAdmin. You may need to ask your web host for info.

gigfish’s picture

gigfish commented

was hoping for a fix tonight im in sydney australia..

gigfish

gpk’s picture

gpk commented

Once you have found out how to manipulate your DB directly then you can try out the suggestion at #1 very easily :-) . If you have shell access you probably have another option -> to use the mysql command line interface ...

Still worth having a look at your webserver logs (again, your host may be able to point you to where you can find them).

gigfish’s picture

gigfish commented

ok im in phpmyadmin - just found some devel files in the browse section. there is the option to delete these,, what do u suggest

i found this over and over again in watchdog

a:4:{s:6:"%error";s:7:"warning";s:8:"%message";s:116:"call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given";s:5:"%file";s:66:"/var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc";s:5:"%line";i:591;}

changed status in system to 0 but no change to site
there was one system devel file with a bootstrap value.. should i make it 0?

help im a little/lot lost, thanks muchly

gigfish

gpk’s picture

gpk commented

OK you probably have a couple of pages of themes and modules listed (see the column "type").

Have a look down for any of the modules you have recently installed. You can use the Edit option (icon of a pen at the LH end of the row) to change status from 1 to 0 for these.

Did you actually enable devel.module, or just put it in your modules folder?

gigfish’s picture

gigfish commented

i just put it in the folder..

gigfish

gpk’s picture

gpk commented

If you just put it in the folder then I'm a bit at a loss as to why you are getting errors from devel_themer_catch_function() since you have to visit the admin -> modules page, check the relevant box (for the Devel Themer module in the case of your watchdog error) and submit the form in order to enable the module. However, just setting the status to 0 completely disables the module - no need to change anything else. Make sure you do this for all the devel modules and also the others you've recently added.

You could also try going into the table {variable} and deleting any row that starts dev_ or devel_. Then go to the table {cache} and hit the Empty option. This should (very nearly!) completely uninstall devel and related modules.

gigfish’s picture

gigfish commented

ok done the cache there was nothing re devel_ or dev in variables..

still no luck what i do get now on my site is - this is a screen dump...

"
Paged not found

* warning: call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 591.
* warning: call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 591.
* warning: call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 591.
* warning: call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 591.
* warning: call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 591.
* warning: call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 591.
* warning: call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 591.
* warning: call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 591.
* warning: call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 591.
* warning: call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 591.
* warning: call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 591.
* warning: call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 591.
* warning: call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 591.
* warning: call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 591.
* warning: call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 591.
* warning: call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 591.
* warning: call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 591.
* warning: call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 591.
* warning: call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 591.
* warning: call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 591.
* warning: call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 591.
* warning: call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 591.
* warning: call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 591.
* warning: call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 591.

"any ideas on this?

gigfish’s picture

gigfish commented

then just refeshed site again and got the below

see link

www.gigfishenterprises.com

so i still cant access admin and all site functions that did exist b4..

am i making progress?

there was one {system} devel file with a bootstrap value.. should i make it 0?

gigfish

gigfish’s picture

gigfish commented

any further ideas did u see my posts?

gigfish

gpk’s picture

gpk commented

From the error messages it looks like the Theme developer (devel_themer) module is still enabled. However it depends on devel.module - if devel is *not* enabled then that might explain the error messages. Alternatively if the module is still enabled in the system table but the files aren't there.

gigfish’s picture

gigfish commented

devel_themer is not there.. any suggestions?

gpk’s picture

gpk commented

> devel_themer is not there

As in .. not in the modules folder, or not present in the {system} table in the DB?

gigfish’s picture

gigfish commented

GPK, must say appreciate your help here hope i can get a full solution soon.

Ive deleted all devel_ files from the plesk left hand menu, ive made all files with any reference to devel in the {system} status 0 including the other modules i added with devel.. ive cached.. i checked the {variables} and also nolonger any reference to devel..

still my site shows it header and title but no login and none of the pages of functionality that id had b4 it crashed

see www.gigfishenterprises.com

do u have any other suggestions - this whole thing has really confused me..
ps when i laoded the modules onto the ftp at the start the site just crashed so i didnt get a chance to actually enable it via the admin section of the drupal site,,, which is what i had done in the past ie when adding image and flash modules so yes im confused to seems to go against the strain of other posts on this subject in the forums..

Kindest,

gigfish

Brett

gigfish’s picture

gigfish commented

a:4:{s:6:"%error";s:7:"warning";s:8:"%message";s:116:"call_user_func_array(): First argumented is expected to be a valid callback, 'devel_themer_catch_function' was given";s:5:"%file";s:66:"/var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc";s:5:"%line";i:591;}

i found the above in watchdog but its not the most recent post the most recent post in watchdog are all "page not found" references

Kindest

gigfish

gigfish’s picture

gigfish commented
StatusFileSize
new Picture 2.png379.9 KB

I can send a screen capture of my plesk {system} if u like...

let me know ?

kindest,

gigfish

six0eight’s picture

six0eight commented

or when u add a module i suggest one at a time to test always make sure all permisiions blocks whatver are configured , and if u do it one by one u will know what is buggn out and u can always just change permissions directly to module folder itself much easier than deleting stuff

i have a bug with messaging im configured but i cant message in simple form to other users

peace

gigfish’s picture

gigfish commented

six0eight,

yes i know now learnt the lesson, there is still an issue i need to fix though and quite critical
plus devel does seem to have quite a few issues......

any ideas?

gigfish

gpk’s picture

gpk commented

Just to clarify: if you were getting errors about a particular module (e.g. devel or devel_themer) then you *must* have enabled that module. You can't get errors just by uploading the module files. Same for a theme.

So is looks like devel is not the problem ... I would strongly suggest disabling all the modules you have recently added by setting their status to 0. Maybe even just go back to the basic set of required core modules (block, filter, node, system, user).

Do a DB backup first, if you've not done one already, in case you just damage the DB further. You could also disable all themes except Garland.

Good luck!

gigfish’s picture

gigfish commented

well its easy for you to say that it cant happen but that is exactly what happened.EXACTLY.. im no drupal expert but i know what happened and how it happended,, sorry to push back but im at a loss...

also i have disabled all modules via changing their status to 0...

ok i will look at diabling and deleting the other modules..

how do i make a backup of the database?

re disabling themes i guess i could try... my main is issue is the above because i did not very clearly activate the devel of other themes so for the benefit of other users who may download it and load it to ftp i think it needs investigation. because whatever the issue is there is an issue..

sorry to be a paid, but this is reality maybe we need to think a little more laterally that simply it cant happen to what circumtances could exist where it could happen..

Kindest and agin thanks for your lone input.. much obliged..

gigfish

gigfish’s picture

gigfish commented

OK TRIED THE ABOVE REMOVED THE MODULES AND REMOVED OTHER THEMES NOT USED..

NOW WEB PAGE SHOWS SOME DAMAGE EVEN TO THE FOURSEASONS THEME I WAS USING.. SEEMS TO ME SOME SORT OF BUG HAS DISTORTED MY DRUPAL SITE..

???? IM LOST

THIS IS THE ERROR MESSAGE AS OF NOW..

visit www.gigfishenterprises.com

Page not found

* warning: _init_theme(./themes/engines/phptemplate/phptemplate.engine): failed to open stream: No such file or directory in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 156.
* warning: _init_theme(): Failed opening './themes/engines/phptemplate/phptemplate.engine' for inclusion (include_path='.:') in /var/www/vhosts/gigfishenterprises.com/httpdocs/includes/theme.inc on line 156.

The requested page could not be found.

please help?

gigfish

gpk’s picture

gpk commented

What has happened is that you appear to have removed the core phptemplate.engine file which is a fundamental component of Drupal.

Moving/removing files will rarely solve a problem, since if Drupal thinks it needs module or file x, then if you remove it you will get an error when Drupal tries to run code from that file or access the file.

I actually suggest you restore all the files you have removed ... your problems need to be fixed in the database and moving/removing files can, as you have found, just make things worse.

For future reference: best not to touch *any* files in the main themes/ or modules/ folders. Modules and themes that you upload should go underneath the sites/ folder, typically in sites/all/modules and sites/all/themes.

>how do i make a backup of the database?
There should be an option in your Plesk control panel to do this.

>i did not very clearly activate the devel of other themes
Just to clarify ... devel is a module, not a theme. But the principle is the same: Drupal does not parse code from any module or theme until the module/theme has been enabled on the modules admin page or the themes admin page. This prevents a module/theme with code errors from trashing a site before the module/theme has been enabled (and also means you can rescue a site by manually setting the status to 0 for a problematic module). The only other way I can think that a module or theme could be enabled is programatically - basically, Drupal only runs code from those items in the {system} table whose status is set to 1. (Drupal *does* parse the .info files without a module/theme being enabled, but these don't contain code.) In theory therefore it is possible for a contributed module to change the values of the status column in the {system} table directly, or to call Drupal's http://api.drupal.org/api/function/module_enable/6 function. However I can't imagine that any normal module would ever do the first (except possibly in very specific, custom situations/implementatinos), and the only situation I know of where module_enable() would be called is if you specify that module B requires module A, in which case module A will automatically be enabled if you enable B. But it is the main Drupal system that handles this - a contrib. module would never (normally) call module_enable().

HTH

gigfish’s picture

gigfish commented

well in geeting frsutrated ive just trued starting again, problem is in the install i have a http 501 error??!!

i have posted a forum topic on that too.

does it ever end so i can just go back to havinbg a functioning site? ive already spent a few weeks.. and now need to start again'

any idea about http 501 error?and how to fix it?
gigfish

gpk’s picture

gpk commented

Well a quick Google search brought up this (among others) http://drupal.org/node/221546#comment-730831

Suggest you check your Apache error logs (via Plesk) to see if you have the same error.

If so it is a server issue (speak to your webhost), and it might also explain your other problems.

As far as "restarting" goes, I would first try using your existing database with a fresh Drupal codebase (of the same version that you started with originally, i.e. 6.1 I think), having first made sure that only the 5 core modules I listed above have status=1, and also make sure all themes have status=0 apart from garland. (You may also have to set the default theme in the database, we'll come to that later if necessary).

On reflection, another possible cause of some of the problems you are having is that you were using Drupal 6.1 but maybe one or more of the modules/themes you tried to use required 6.2. There is a principle that all 6.x modules should work with all 6.x versions of Drupal, but there was a bug in 6.0/6.1 which meant that all modules which worked with 6.0/6.1 had to be updated to work properly with 6.2, and possibly 6.2-compatible modules won't work with 6.0/6.1. This may well not be the problem of course, just another thought, and the approach above would be the best way of going forwards.

If you do get your 6.1 database going again, probably a good idea as the next step to update to 6.2, then make sure any modules you download are compatible with 6.2.

Or just email me your DB ;-)

ainigma32’s picture

ainigma32 commented
Status: Active » Fixed

@gigfish: It looks like you got your site up and running so I'm going to assume this issue was resolved.

Feel free to reopen if that is incorrect.

- Arie

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.