Re: PHP db will not allow modifications
Date: Tue, 06 Nov 2018 18:46:02 -0500
Message-ID: <prt93t$jse$1_at_dont-email.me>
Lew Pitcher wrote:
> super70s wrote: >
>> Hi, I have an article directory site that runs on php. I have added 1800
>> articles to it over the past few years as I have time. Lately I've
>> noticed in the Admin Panel of the site (not the Cpanel of the server)
>> that it will not accept modifications to existing articles. Also
>> sometimes the browser will crash when I try that. Could these problems
>> be due to the db becoming too huge? The Admin Panel is accepting new
>> articles as normal though and they are displaying on the site.
>>
>> In my server cPanel under "MySQL Databases," it did not say anything was
>> wrong with the db and when I checked it, I got this result:
>>
>> [articlesite_artic.article_master] OK
>> [articlesite_artic.category_master] OK
>> [articlesite_artic.document_master] OK
>> [articlesite_artic.settings] OK
>> [articlesite_artic.user_master] OK
>>
>> But I went ahead and did a "repair" on it anyway, and the message was
>> "db repaired."
>>
>> When I tried to modify an existing article, the problem remained.
>>
>> Any thoughts?
This was my WAG, posted during TV commercials... > Check the MySQL user privileges; does it include UPDATE privileges on the > relevant databases?
Now, on to the real answer.
You asked
>> Any thoughts?
Yes, a few.
First off, you've given us exactly NO detail about the problem you are having. You say that you have "an article directory site that runs on php", and that "it will not accept modifications to existing articles".
You /don't/ say whether there are any other technologies beyond the (inferred) HTML, PHP and MySQL technologies that you already mention. Choice of web browser, use of Javascript, client/server framework, server technology, all these factors, and more, can influence whether or not a webbased application "works" or not.
Additionally, you /don't/ say what sort of errors you see, either in your web logs or your MySQL logs. You /don't/ say even if you /have looked/ at the error logs.
In other words, there's no true indication that PHP or MySQL are interfering with your ability to update your stored data.
And, so, the WAG. A deficiency in MySQL user privileges /can/ cause databases to not update. You /should/ see some sort of error, logged to MySQL. You /may/ see some sort of error logged by PHP to your web log (it depends on what the PHP code does on MySQL Query errors). You /might even/ see something on the displayed web page (again, depending on how the PHP externalizes errors).
To get a better idea of what the problem is, you should perform some rudementary diagnostics yourself, such as looking for patterns in the update failures, checking the logs and web pages for error messages, performing manual updates using a MySQL client, etc.
/If/, after all that, you still have a problem, post your research (*ALL* of your research), and ask a question. Before you repost and ask, please read http://www.catb.org/esr/faqs/smart-questions.html for hints and clues about /what/ you need to post, and /what/ you need to ask.
Luck be with you
-- Lew Pitcher "In Skills, We Trust"Received on Wed Nov 07 2018 - 00:46:02 CET