Drupal: Issue in DruTex - php

I have installed and configured DruTex (in my Drupal6 installation).
But when I go to create a page, a warning appears on the top of the page as:
warning: Parameter 1 to drutex_pdf_nodeapi() expected to be a reference, value given in /usr/share/drupal6/modules/drutex/drutex.module on line 829.
Please help me in removing it.
Note: I used a # in the mentioned file on line 829 however then following errors come when I create a page :
TeX Embedding failed!

Related

File wp-db.php is deprecated since version 6.1.0! Use wp-includes/class-wpdb.php instead

After an automatic update to my WordPress installation, my website is display this error rather than loading.
Deprecated: File wp-db.php is deprecated since version 6.1.0! Use wp-includes/class-wpdb.php instead. in /home/vol13_4/epizy.com/epiz_30367402/htdocs/wp-includes/functions.php on line 5595
Warning: require(/home/vol13_4/epizy.com/epiz_30367402/htdocs/wp-includes/class-wp-dependencies.php): failed to open stream: No such file or directory in /home/vol13_4/epizy.com/epiz_30367402/htdocs/wp-includes/script-loader.php on line 23
Fatal error: require(): Failed opening required '/home/vol13_4/epizy.com/epiz_30367402/htdocs/wp-includes/class-wp-dependencies.php' (include_path='.:/usr/share/pear/') in /home/vol13_4/epizy.com/epiz_30367402/htdocs/wp-includes/script-loader.php on line 23
Notice: Function is_embed was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /home/vol13_4/epizy.com/epiz_30367402/htdocs/wp-includes/functions.php on line 5835
Notice: Function is_search was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /home/vol13_4/epizy.com/epiz_30367402/htdocs/wp-includes/functions.php on line 5835
There has been a critical error on this website.
Can someone help me understand this error, and provide me a solution or some hints so that I can figure a fix for this.
I also had the same problem currently. So here's how I fixed it.
Go to your Website's App Installer > Wordpress > and find something like this
https://i.stack.imgur.com/xvhm0.png
Click the one in the blue box i drew at the right (Wordpress Manager)
Then, there you can update wordpress
Hope it helped!
i solved it just by updating all plugins, idk why it worked but you can give it a try.

Apache server log error. AH00126: Invalid URI in request GET, etc

I checked the server log recently, there are so many error types.
1 . AH00126: Invalid URI in request GET /../../terms HTTP/1.1 .
This kind of error is the most common one, our website is on Wordpress. This page is on www.MYSITENAME.com/terms. I check most of the pages, and checked the links, all of them did not cause this invalid Request.
But if I use postman, type the URL directly, like: www.MYSITENAME.com/../terms, this would cause the error and also it would be catched and logged.
Any idea about this error? I search it on google, someone said it is the problem from the .htaccess file, but I dont really understand it.
2. PHP Warning: mysqli_query(): (00000/0): in /var/www/www.MYSITENAME.com/public_html/wp-includes/wp-db.php on line 2007
I have no idea about this one.
3. PHP Fatal error: Out of memory (allocated 20971520) (tried to allocate 77824 bytes)
4. PHP Warning: Error while sending QUERY packet. PID=22936 in /var/www/www.MYSITENAME.com/public_html/wp-includes/wp-db.php on line 2007
5. PHP Warning: mysqli_real_escape_string() expects parameter 1 to be mysqli, null given in /var/www/www.MYSITENAME.com/public_html/wp-content/plugins/wp-cerber/common.php on line 1968
6. PHP Warning: mysqli_query() expects parameter 1 to be mysqli, null given in /var/www/www.MYSITENAME.com/public_html/wp-content/plugins/wp-cerber/common.php on line 2017
Any idea about Any error?
Thanks.
For the first error:[ AH00126: Invalid URI in request GET /../../terms HTTP/1.1 .], I found out where was going wrong. On my site, sitting on wordpress and also editting from wordpress, we used the relative URL before. Now we fix it to the absolute one.
I have searched for some relevant questions, someone said this kind of problem is caused by crawler program, but others said .htaccess leads the problem. But I do recommend just go through your own code about the URL parts first

MediaWiki 1.27 warning requiring SpecialUserLogin.php

I've updated my mediawiki from 1.26.2 to 1.27, the installation process finished ok, but when I try to access I received this error:
Warning:
require(/var/app/current/includes/specials/SpecialUserLogin.php):
failed to open stream: No such file or directory in
/var/app/current/includes/AutoLoader.php on line 81 Fatal error:
require(): Failed opening required
'/var/app/current/includes/specials/SpecialUserLogin.php'
(include_path='/var/app/current/vendor/pear/pear_exception:/var/app/current/vendor/pear/console_getopt:/var/app/current/vendor/pear/pear-core-minimal/src:/var/app/current/vendor/pear/mail_mime:/var/app/current/vendor/pear/mail_mime-decode:/var/app/current/vendor/pear/net_socket:/var/app/current/vendor/pear/net_smtp:/var/app/current/vendor/pear/mail:.:/usr/share/pear:/usr/share/php')
in /var/app/current/includes/AutoLoader.php on line 81
I have no idea why is this happening. If I check the files in my server they're there. I'm also having template issues if I choose vector I only get a messed up template, without styling.
I'm using PHP 5.6.
I hope someone can help me.
I just stumbled across this same exact error after upgrading to MW 1.27.
In my case, the SpecialUserlogin.php existed and all of the permissions were right BUT the word login was written in lowercase so the system thought this file didn't exist. So I just renamed the SpecialUserlogin.php to SpecialUserLogin.php and b00m, it worked!
As for your templating issues, check the common.css file. Copy paste everything out of there, so it's empty, if you don't use it. And check that you're calling your style files correctly in your template.

Wordpress - Warning: call_user_func_array() expects parameter 1 to be a valid callback

I am trying move my wordpress website from one host to another.
I downloaded the website backup and database backup from the previous host.
I uploaded the WP files to the newhost. I uploaded the database to the new host's database.
I updated wp-config.php.
Then whent I tried to access my website, I got the below error. I am very confused what goes wrong.
I got the below errors.
Warning: call_user_func_array() expects parameter 1 to be a valid
callback, function 'wp_enqueue_scripts' not found or invalid function
name in /wp-includes/plugin.php on line 496
Warning: call_user_func_array() expects parameter 1 to be a valid callback, function 'wp_print_styles' not found or invalid function
name in /wp-includes/plugin.php on line 496
Warning: call_user_func_array() expects parameter 1 to be a valid callback, function 'wp_print_head_scripts' not found or invalid
function name in /wp-includes/plugin.php on line 496
Also I am not able to see the admin part also.
I tried to disable plugins via database to check whether any plugin conflicts with the site. But it went in vain.
My theme stylesheet is broken. Also some of the image urls showing the older host's url. I am really confused about what is wrong?
If you need any more info, kindly ask in comments.
I walked into something similar.
My problem was that some of the files were completely missing from the Wordpress folder (I still don't know how that happened). But anyway, I got a fresh copy of wordpress, installed it, then moved my themes and reinstalled all plugins, and everything was back to normal.
Hopefully this could help you.
Re-installing the WP core fixed this problem for me.

Mage::app()->setCurrentStore(Mage_Core_Model_App::ADMIN_STORE_ID); leads into a fatal error

A Magento extension I installed has a line of code that leads into a fatal error.
I'm using Magento 1.8.0 and when I remove this line everything works like expected.
Mage::app()->setCurrentStore(Mage_Core_Model_App::ADMIN_STORE_ID);
Can somebody please explain what this line of code does and why its needed in the extension.
After I commented this line out everything works fine and I couldn't find any kind of problem, but I'm a bit scarred that the problem will come up later.
Here is what the system log file throws:
2014-08-27T21:10:13+00:00 ERR (3): Warning: include(Mage/Default/Helper/Data.php): failed to open stream: No such file or directory in /homepages/11/d460572798/htdocs/magento/lib/Varien/Autoload.php on line 93
2014-08-27T21:10:13+00:00 ERR (3): Warning: include(): Failed opening 'Mage/Default/Helper/Data.php' for inclusion (include_path='/homepages/11/d460572798/htdocs/magento/app/code/local:/homepages/11/d460572798/htdocs/magento/app/code/community:/homepages/11/d460572798/htdocs/magento/app/code/core:/homepages/11/d460572798/htdocs/magento/lib:.:/usr/lib/php5.4') in /homepages/11/d460572798/htdocs/magento/lib/Varien/Autoload.php on line 93
I'm a complete newbie in programming of Magento.
The code is use to set current store that using by Magento
Mage::app()->setCurrentStore(Mage_Core_Model_App::ADMIN_STORE_ID);
Magento uses store with id zero for admin side. Frontend may have any number of stores. So they don't have fixed store id. But admin side always has its store id zero and is fixed.
So the extension, due to some reason trying to use admin store forcefully. May be that line added in the extension during the development of the extension (for testing purpose). But not sure.
From the question, it is not sure where that code is using. So I cant say whether the code is essential or not. But if the problem solves when comment out that line and if there is no log errors present, you are good to go. Feel free to comment out that line.
The error that is showing in log errors are showing due to this line (A wild guess).
If you need more details, you need to ask this quesition to developers who created that extesnion :)

Categories