After the update my entries no longer appear on my screen. Any suggestions?

After setting debug on I got the following errors:

MySQL Error: 0
Query: SELECT pm_value FROM pm_prefs WHERE pm_option = ‘display_posts_by_weblog’

MySQL Error: 0
Query: SELECT pm_value FROM pm_prefs WHERE pm_option = ‘posts_per_page_weblog’

MySQL Error: 0
Query: SELECT pm_value FROM pm_prefs WHERE pm_option = ‘posts_by_month_weblog’

MySQL Error: 0
Query: SELECT pm_value FROM pm_prefs WHERE pm_option = ‘timeoffset’

MySQL Error: 0
Query: SELECT pm_value FROM pm_prefs WHERE pm_option = ‘memdir’

MySQL Error: 0
Query: SELECT pm_value FROM pm_prefs WHERE pm_option = ‘libdir’

MySQL Error: 0
Query: SELECT pm_value FROM pm_prefs WHERE pm_option = ‘pages_path_abs_weblog’

MySQL Error: 0
Query: SELECT pm_value FROM pm_prefs WHERE pm_option = ‘display_order_weblog’

MySQL Error: 0
Query: SELECT pm_value FROM pm_prefs WHERE pm_option = ‘date_and_time_weblog’

MySQL Error: 0
Query: SELECT pm_value FROM pm_prefs WHERE pm_option = ‘html_display_options_weblog’

MySQL Error: 0
Query: SELECT pm_value FROM pm_prefs WHERE pm_option = ‘weblog_page’

MySQL Error: 0
Query: SELECT pm_value FROM pm_prefs WHERE pm_option = ‘comments_page_weblog’

MySQL Error: 0
Query: SELECT pm_value FROM pm_prefs WHERE pm_option = ‘more_page_weblog’

MySQL Error: 0
Query: SELECT pm_value FROM pm_prefs WHERE pm_option = ‘trackbacks_page_weblog’

MySQL Error: 0
Query: SELECT pm_value FROM pm_prefs WHERE pm_option = ‘pingbacks_page_weblog’

MySQL Error: 0
Query: SELECT pm_value FROM pm_prefs WHERE pm_option = ‘row_color_one_weblog’

MySQL Error: 0
Query: SELECT pm_value FROM pm_prefs WHERE pm_option = ‘row_color_two_weblog’

MySQL Error: 0
Query: SELECT pm_value FROM pm_prefs WHERE pm_option = ‘weblog_templategroup’

MySQL Error: 0
Query: SELECT pm_value FROM pm_prefs WHERE pm_option = ‘word_censor_weblog’

MySQL Error: 0
Query: SELECT pm_value FROM pm_prefs WHERE pm_option = ‘trackback_weblog’

MySQL Error: 0
Query: SELECT pm_value FROM pm_prefs WHERE pm_option = ‘link_opens_window_weblog’

MySQL Error: 0
Query: SELECT body FROM pm_templates WHERE cat_name = ‘’ AND template_id = ‘05’

MySQL Error: 0
Query: SELECT body FROM pm_templates WHERE cat_name = ‘’ AND template_id = ‘10’

MySQL Error: 0
Query: SELECT body FROM pm_templates WHERE cat_name = ‘’ AND template_id = ‘20’

MySQL Error: 0
Query: SELECT body FROM pm_templates WHERE cat_name = ‘’ AND template_id = ‘30’

MySQL Error: 0
Query: SELECT body FROM pm_templates WHERE cat_name = ‘’ AND template_id = ‘40’

MySQL Error: 0
Query: select id from pm_multiweblogs where weblog = ‘weblog’

MySQL Error: 0
Query: select id,category from pm_categories order by id

MySQL Error: 0
Query: select id,abspath from pm_upload_prefs order by id

MySQL Error: 0
Query: select count(*) as count from pm_weblog where weblog = ‘weblog’ and status = ‘open’ and preview != ‘1’ and t_stamp <= ‘1105963636’ and x_stamp >= ‘1105963636’

MySQL Error: 0
Query: select * from pm_weblog where weblog = ‘weblog’ and status = ‘open’ and preview != ‘1’ and t_stamp <= ‘1105963636’ and x_stamp >= ‘1105963636’ order by sticky DESC, t_stamp desc limit 0, 10

If you use something like phpMyAdmin to look at your database do you have the expected content in your tables?

Yes, as far as I can see all the info is in de database. If I use the controlpanel I can also view en edit my entries. The only problem is that the don’t appear on my homepage, like the did before updating.

This is the code I have inside my index.php that used to work before the update. Did anything chage perhaps?

<?php weblog_entries($id,“weblog”); ?>

(of course <?php include(“pm_inc.php”); ?> is also in the index file)

All of those queries should work.  Have you tried using phpMyAdmin and running those queries via their SQL tab?

When you updated, did you remember to copy over your database information in the config.php file?

Hi Paul,

I copied the informatie over to the new config.php. When I run the queries in phpMyAdmin the seem to work, but not on my index file. Strange. It worked fine before updating.

Any other suggestions?

Hm, there are two places this will occur:  When pMachine is unable to connect to the database (invalid database, bad permssions, or empty database name) -or- the query fails. 

Now, a 0 error number means there was not error, but for some reason MySQL is still failing the query.  Very odd.  What version of PHP and MySQL are you using?

The version of MySQL is 3.23.58 and the php-version is 4.3.10

I placed back the all the old files of the pm directory and then it works. Could there be a problem with the database name? My name has dashes:
marcjager_nl_-_mjj

What changes does the “updater” make to the database?

Well, the updater just adds about five tables, modifies two, and adds a slew of preference.  If putting the old files backs fixes the problem and you did not revert the database back, then it seems to be a problem with the database file.

We have others running similar versions of PHP and MySQL, and no one is reporting these odd errors.  Mind if I take a look at your site/server?

Paul, I am having the same exact problem. I get MySQL Error: 0s. The forum part of the website works just fine, but the main index is broken and full of these MySQL errors.

Do you have a solution to this problem? The mysql user on our site has ALL privileges.

Thanks,

dombi

I believe that these is some kind of a bug in the new 2.4 code. I replaced the pm directory with the new one, and things are working again. I looked at several functions within the pm directory and they have changed for sure. There are new global variables, new database calls.

Something is definitely up with the new code, since I am having this same problem. What is really strange is that the forums work just fine. Registration and member section works well as well, the only problems some from the weblog related pmachine tags.

We are running
PHP version: 4.3.10
MySQL version: 4.0.22-standard

Here are the tags that are failing for sure:

<?php weblog_entries($id,“weblog”); ?>
<?php weblog_title_list($wtl); ?>
<?php weblog_stats(“weblog”); ?>
<?php comment_stats(“weblog”); ?>
<?php member_stats(); ?>
<?php hit_counter(); ?>

I think this would be a good place to start debugging. Please let me know what is going on here, becasue pmachine 2.4 is not usabe in this form.

Thank you,

dombi

> I replaced the pm directory with the new one, and things are working again

I assume you actually meant something else?

I replaced the pm directory with the new one, and things are working again

Sorry, you are correct. Before I uploaded the new (2.4) pm directory, I renamed the old one to something else (just in case). After seeing that the new one did not work and caused all these MySQL problems, I placed the old pm directory back, which works. Of course this way the website does not have all the new security features and additions.

So currenlty I can switch back and forth between the new and old diretories for testing. There is definitely something wrong with the new one. The functions I mentioned above do not work for some reason, they all come back with “MySQL error: 0"s and then the query. When I manually run the query in phpMyAdmin everything goes through just fine.

I still have the same problem. Due to a lack of time I did not look at it again, but if you can give me some suggestions I will try it again.

If you guys want to send me FTP and login information, I can look at your sites and see why MySQL is returning false on your queries when there is no error.  Considering we have two people with this problem and likely have over a thousand of people using pMachine 2.4 already there is probably something wonky going on.

OK, I have a new db.mysql.php file that I need the people with this problem to test.  It seems if you are using any PHP code or scripts that connect to MySQL or a different database, it might cause problems.

I’m having the same problem also. Just upgraded from 2.3 Free to 2.4 Pro. The site seems to be working for the most part, save several “MySQL Error: 0” errors on the sidebar (php calls for pBlocks, search form, and archives.) This error only occurs on the main index.php page, not on other pages (same calls work fine on other pages such as comments or archives).

Any ideas/fixes/help? Does the new db.mysql.php file help?

The new db.mysql.php file is in the current downloadable files as of about a week ago.