Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.databases.mysql > #6994 > unrolled thread

PHP db will not allow modifications

Back to article view | Back to comp.databases.mysql

Contents

  PHP db will not allow modifications super70s <super70s@super70s.invalid> - 2018-11-06 15:39 -0600
    Re: PHP db will not allow modifications Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2018-11-06 17:40 -0500
      Re: PHP db will not allow modifications Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2018-11-06 18:46 -0500
    Re: PHP db will not allow modifications Luuk <luuk@invalid.lan> - 2018-11-07 14:46 +0100
      Re: PHP db will not allow modifications super70s <super70s@super70s.invalid> - 2018-11-08 05:48 -0600
        Re: PHP db will not allow modifications Jerry Stuckle <jstucklex@attglobal.net> - 2018-11-08 09:30 -0500
          Re: PHP db will not allow modifications Martin Gregorie <martin@mydomain.invalid> - 2018-11-08 15:56 +0000
            Re: PHP db will not allow modifications super70s <super70s@super70s.invalid> - 2018-11-09 00:44 -0600
              Re: PHP db will not allow modifications Jerry Stuckle <jstucklex@attglobal.net> - 2018-11-09 22:11 -0500
                Re: PHP db will not allow modifications The Natural Philosopher <tnp@invalid.invalid> - 2018-11-10 08:30 +0000
                  Re: PHP db will not allow modifications Jerry Stuckle <jstucklex@attglobal.net> - 2018-11-10 08:34 -0500
                    Re: PHP db will not allow modifications Martin Gregorie <martin@mydomain.invalid> - 2018-11-10 18:09 +0000
                      Re: PHP db will not allow modifications The Natural Philosopher <tnp@invalid.invalid> - 2018-11-10 18:12 +0000
                        Re: PHP db will not allow modifications Jerry Stuckle <jstucklex@attglobal.net> - 2018-11-10 18:02 -0500
        Re: PHP db will not allow modifications Luuk <luuk@invalid.lan> - 2018-11-08 19:01 +0100
          Re: PHP db will not allow modifications The Natural Philosopher <tnp@invalid.invalid> - 2018-11-08 18:38 +0000
            Re: PHP db will not allow modifications Jerry Stuckle <jstucklex@attglobal.net> - 2018-11-10 08:36 -0500
    Re: PHP db will not allow modifications Percival John Hackworth <pjh@nanoworks.com> - 2018-11-07 08:44 -0800

#6994 — PHP db will not allow modifications

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?

[toc] | [next] | [standalone]

#6995

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?

Check the MySQL user privileges; does it include UPDATE privileges on the 
relevant databases?

-- 
Lew Pitcher
"In Skills, We Trust"

[toc] | [prev] | [next] | [standalone]

#6996

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 web-
based 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"

[toc] | [prev] | [next] | [standalone]

#6997

On 6-11-2018 22:39, 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?
> 

Are you using the correct statement to update this table?

What is the exact error message that is given when you try to update an
article?

[toc] | [prev] | [next] | [standalone]

#6999

In article <5be2ecc4$0$32263$e4fe514c@news.xs4all.nl>,
 Luuk <luuk@invalid.lan> wrote:

> Are you using the correct statement to update this table?
> 
> What is the exact error message that is given when you try to update an
> article?

The message in the "New Article" window says "Article Information Saved" 
as normal, however it refuses to accept the modification.

I'm afraid I don't have a lot of experience with this, in fact I had to 
hire someone to install the db so I apologize if I "offended anyone's 
senses."

It isn't that big a deal really, I'm pretty good at proofreading the 
articles before I post them but sometimes I'll spot a small typo or 
something and want to go back and correct it (until now, lol).

[toc] | [prev] | [next] | [standalone]

#7000

On 11/8/2018 6:48 AM, super70s wrote:
> In article <5be2ecc4$0$32263$e4fe514c@news.xs4all.nl>,
>   Luuk <luuk@invalid.lan> wrote:
> 
>> Are you using the correct statement to update this table?
>>
>> What is the exact error message that is given when you try to update an
>> article?
> 
> The message in the "New Article" window says "Article Information Saved"
> as normal, however it refuses to accept the modification.
> 
> I'm afraid I don't have a lot of experience with this, in fact I had to
> hire someone to install the db so I apologize if I "offended anyone's
> senses."
> 
> It isn't that big a deal really, I'm pretty good at proofreading the
> articles before I post them but sometimes I'll spot a small typo or
> something and want to go back and correct it (until now, lol).
> 

It sounds like you aren't checking the result codes from your SQL 
statements, so your script does not tell you when a request failed.

You should check the result of *every* database request - or you'll run 
into problems like this.  Fix your code and see what the failure is.

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#7001

On Thu, 08 Nov 2018 09:30:42 -0500, Jerry Stuckle wrote:

> On 11/8/2018 6:48 AM, super70s wrote:
>> In article <5be2ecc4$0$32263$e4fe514c@news.xs4all.nl>,
>>   Luuk <luuk@invalid.lan> wrote:
>> 
>>> Are you using the correct statement to update this table?
>>>
>>> What is the exact error message that is given when you try to update
>>> an article?
>> 
>> The message in the "New Article" window says "Article Information
>> Saved"
>> as normal, however it refuses to accept the modification.
>> 
>> I'm afraid I don't have a lot of experience with this, in fact I had to
>> hire someone to install the db so I apologize if I "offended anyone's
>> senses."
>> 
>> It isn't that big a deal really, I'm pretty good at proofreading the
>> articles before I post them but sometimes I'll spot a small typo or
>> something and want to go back and correct it (until now, lol).
>> 
>> 
> It sounds like you aren't checking the result codes from your SQL
> statements, so your script does not tell you when a request failed.
> 
> You should check the result of *every* database request - or you'll run
> into problems like this.  Fix your code and see what the failure is.

...and don't forget that some SQL statements generate a linked chain of 
exception messages if they fail. Trapping the first exception may tell 
your code that there is a problem and what sort it is, but if its fatal 
you probably need to see all the exceptions in the chain to understand 
what went wrong.


-- 
Martin    | martin at
Gregorie  | gregorie dot org

[toc] | [prev] | [next] | [standalone]

#7004

In article <ps1mag$n8m$1@news.albasani.net>,
 Martin Gregorie <martin@mydomain.invalid> wrote:

> On Thu, 08 Nov 2018 09:30:42 -0500, Jerry Stuckle wrote:
> 
> > On 11/8/2018 6:48 AM, super70s wrote:
> >> In article <5be2ecc4$0$32263$e4fe514c@news.xs4all.nl>,
> >>   Luuk <luuk@invalid.lan> wrote:
> >> 
> >>> Are you using the correct statement to update this table?
> >>>
> >>> What is the exact error message that is given when you try to update
> >>> an article?
> >> 
> >> The message in the "New Article" window says "Article Information
> >> Saved"
> >> as normal, however it refuses to accept the modification.
> >> 
> >> I'm afraid I don't have a lot of experience with this, in fact I had to
> >> hire someone to install the db so I apologize if I "offended anyone's
> >> senses."
> >> 
> >> It isn't that big a deal really, I'm pretty good at proofreading the
> >> articles before I post them but sometimes I'll spot a small typo or
> >> something and want to go back and correct it (until now, lol).
> >> 
> >> 
> > It sounds like you aren't checking the result codes from your SQL
> > statements, so your script does not tell you when a request failed.
> > 
> > You should check the result of *every* database request - or you'll run
> > into problems like this.  Fix your code and see what the failure is.
> 
> ...and don't forget that some SQL statements generate a linked chain of 
> exception messages if they fail. Trapping the first exception may tell 
> your code that there is a problem and what sort it is, but if its fatal 
> you probably need to see all the exceptions in the chain to understand 
> what went wrong.

I guess a workaround could be to simply delete the article that needs 
the modification, make the correction, then repost it as a new article. 
But I'd lose any "link juice" that URL had.

[toc] | [prev] | [next] | [standalone]

#7005

On 11/9/2018 1:44 AM, super70s wrote:
> In article <ps1mag$n8m$1@news.albasani.net>,
>   Martin Gregorie <martin@mydomain.invalid> wrote:
> 
>> On Thu, 08 Nov 2018 09:30:42 -0500, Jerry Stuckle wrote:
>>
>>> On 11/8/2018 6:48 AM, super70s wrote:
>>>> In article <5be2ecc4$0$32263$e4fe514c@news.xs4all.nl>,
>>>>    Luuk <luuk@invalid.lan> wrote:
>>>>
>>>>> Are you using the correct statement to update this table?
>>>>>
>>>>> What is the exact error message that is given when you try to update
>>>>> an article?
>>>>
>>>> The message in the "New Article" window says "Article Information
>>>> Saved"
>>>> as normal, however it refuses to accept the modification.
>>>>
>>>> I'm afraid I don't have a lot of experience with this, in fact I had to
>>>> hire someone to install the db so I apologize if I "offended anyone's
>>>> senses."
>>>>
>>>> It isn't that big a deal really, I'm pretty good at proofreading the
>>>> articles before I post them but sometimes I'll spot a small typo or
>>>> something and want to go back and correct it (until now, lol).
>>>>
>>>>
>>> It sounds like you aren't checking the result codes from your SQL
>>> statements, so your script does not tell you when a request failed.
>>>
>>> You should check the result of *every* database request - or you'll run
>>> into problems like this.  Fix your code and see what the failure is.
>>
>> ...and don't forget that some SQL statements generate a linked chain of
>> exception messages if they fail. Trapping the first exception may tell
>> your code that there is a problem and what sort it is, but if its fatal
>> you probably need to see all the exceptions in the chain to understand
>> what went wrong.
> 
> I guess a workaround could be to simply delete the article that needs
> the modification, make the correction, then repost it as a new article.
> But I'd lose any "link juice" that URL had.
> 

No, the "workaround" is to correct your code.

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#7006

On 10/11/2018 03:11, Jerry Stuckle wrote:
> No, the "workaround" is to correct your code.

Its not his code.

Wanker.


-- 
“The fundamental cause of the trouble in the modern world today is that 
the stupid are cocksure while the intelligent are full of doubt."

    - Bertrand Russell

[toc] | [prev] | [next] | [standalone]

#7007

On 11/10/2018 3:30 AM, The Natural Philosopher wrote:
> On 10/11/2018 03:11, Jerry Stuckle wrote:
>> No, the "workaround" is to correct your code.
> 
> Its not his code.
> 
> Wanker.
> 
> 

He may not have written it - but it's still his code.  Idiot.

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#7009

On Sat, 10 Nov 2018 08:34:37 -0500, Jerry Stuckle wrote:

> On 11/10/2018 3:30 AM, The Natural Philosopher wrote:
>> On 10/11/2018 03:11, Jerry Stuckle wrote:
>>> No, the "workaround" is to correct your code.
>> 
>> Its not his code.
>> 
>> Wanker.
>> 
>> 
>> 
> He may not have written it - but it's still his code.  Idiot.

Tush Tush Tush.

I'm inclined to agree with Jerry here: the OP's answers look more like 
something a user would say as opposed to even an inexperienced sysadmin 
or developer.

So, to the OP: if I've guessed right, you should raise this with your 
website's help desk if they provide you with access to a publishing 
package that they installed and maintain or, if you've installed the 
publishing package yourself, ask the package's authors for help or raise 
a bug against it. 

comp.lang.php is a discussion and self-help forum for developers capable 
of writing and maintaining PHP code rather than those using PHP packages 
that others maintain and/or modify. This explains why you're being given 
answers suitable for a PHP programmer rather than the PHP package user 
you would seem to be.


-- 
Martin    | martin at
Gregorie  | gregorie dot org

[toc] | [prev] | [next] | [standalone]

#7010

On 10/11/2018 18:09, Martin Gregorie wrote:
> On Sat, 10 Nov 2018 08:34:37 -0500, Jerry Stuckle wrote:
> 
>> On 11/10/2018 3:30 AM, The Natural Philosopher wrote:
>>> On 10/11/2018 03:11, Jerry Stuckle wrote:
>>>> No, the "workaround" is to correct your code.
>>>
>>> Its not his code.
>>>
>>> Wanker.
>>>
>>>
>>>
>> He may not have written it - but it's still his code.  Idiot.
> 
> Tush Tush Tush.
> 
How can he correct it when its not his code?

> I'm inclined to agree with Jerry here: the OP's answers look more like
> something a user would say as opposed to even an inexperienced sysadmin
> or developer.

Exactly. Its not his code. He rents space on a systemn and he rents code.

> So, to the OP: if I've guessed right, you should raise this with your
> website's help desk if they provide you with access to a publishing
> package that they installed and maintain or, if you've installed the
> publishing package yourself, ask the package's authors for help or raise
> a bug against it.
> 
> comp.lang.php is a discussion and self-help forum for developers capable
> of writing and maintaining PHP code rather than those using PHP packages
> that others maintain and/or modify. This explains why you're being given
> answers suitable for a PHP programmer rather than the PHP package user
> you would seem to be.
> 
> 
As I said, you are agreeing with me. It's not his code.

Otherwise he wouldnt have to take it up with his websites helpdesk.


-- 
Renewable energy: Expensive solutions that don't work to a problem that 
doesn't exist instituted by self legalising protection rackets that 
don't protect,  masquerading as public servants who don't serve the public.

[toc] | [prev] | [next] | [standalone]

#7011

On 11/10/2018 1:12 PM, The Natural Philosopher wrote:
> On 10/11/2018 18:09, Martin Gregorie wrote:
>> On Sat, 10 Nov 2018 08:34:37 -0500, Jerry Stuckle wrote:
>>
>>> On 11/10/2018 3:30 AM, The Natural Philosopher wrote:
>>>> On 10/11/2018 03:11, Jerry Stuckle wrote:
>>>>> No, the "workaround" is to correct your code.
>>>>
>>>> Its not his code.
>>>>
>>>> Wanker.
>>>>
>>>>
>>>>
>>> He may not have written it - but it's still his code.  Idiot.
>>
>> Tush Tush Tush.
>>
> How can he correct it when its not his code?
> 
>> I'm inclined to agree with Jerry here: the OP's answers look more like
>> something a user would say as opposed to even an inexperienced sysadmin
>> or developer.
> 
> Exactly. Its not his code. He rents space on a systemn and he rents code.
> 
>> So, to the OP: if I've guessed right, you should raise this with your
>> website's help desk if they provide you with access to a publishing
>> package that they installed and maintain or, if you've installed the
>> publishing package yourself, ask the package's authors for help or raise
>> a bug against it.
>>
>> comp.lang.php is a discussion and self-help forum for developers capable
>> of writing and maintaining PHP code rather than those using PHP packages
>> that others maintain and/or modify. This explains why you're being given
>> answers suitable for a PHP programmer rather than the PHP package user
>> you would seem to be.
>>
>>
> As I said, you are agreeing with me. It's not his code.
> 
> Otherwise he wouldnt have to take it up with his websites helpdesk.
> 
> 

It makes no difference if he wrote it or not.  It is his website, and he 
is responsible for it.  If someone else wrote the code for him, it is 
still his responsibility to take it up with them.

Just because he did not write the code does not mean he is not 
responsible for it.  But ditch diggers like you don't understand things 
like that.

I suggest you go back and try to figure out which end of the shovel to 
use.  You might be able to get a job.  We know you aren't a programmer.

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#7002

On 8-11-2018 12:48, super70s wrote:
> In article <5be2ecc4$0$32263$e4fe514c@news.xs4all.nl>,
>  Luuk <luuk@invalid.lan> wrote:
> 
>> Are you using the correct statement to update this table?
>>
>> What is the exact error message that is given when you try to update an
>> article?
> 
> The message in the "New Article" window says "Article Information Saved" 
> as normal, however it refuses to accept the modification.
> 

OK, your application is telling you "the information is saved", but you
do not see the info in your database.

> I'm afraid I don't have a lot of experience with this, in fact I had to 
> hire someone to install the db so I apologize if I "offended anyone's 
> senses."

You indicate not to have experience with this db.

How should we know what went wrong if we only see the descriptions of
wat want wrong, and do not see any logging, or any SQL statements?
(or, for the PHP part, any PHP-code)

> 
> It isn't that big a deal really, I'm pretty good at proofreading the 
> articles before I post them but sometimes I'll spot a small typo or 
> something and want to go back and correct it (until now, lol).
> 

[toc] | [prev] | [next] | [standalone]

#7003

On 08/11/2018 18:01, Luuk wrote:
> On 8-11-2018 12:48, super70s wrote:
>> In article <5be2ecc4$0$32263$e4fe514c@news.xs4all.nl>,
>>   Luuk <luuk@invalid.lan> wrote:
>>
>>> Are you using the correct statement to update this table?
>>>
>>> What is the exact error message that is given when you try to update an
>>> article?
>>
>> The message in the "New Article" window says "Article Information Saved"
>> as normal, however it refuses to accept the modification.
>>
> 
> OK, your application is telling you "the information is saved", but you
> do not see the info in your database.
> 
>> I'm afraid I don't have a lot of experience with this, in fact I had to
>> hire someone to install the db so I apologize if I "offended anyone's
>> senses."
> 
> You indicate not to have experience with this db.
> 
> How should we know what went wrong if we only see the descriptions of
> wat want wrong, and do not see any logging, or any SQL statements?
> (or, for the PHP part, any PHP-code)

I think that is the point...

he doesnt have access to admin level or indeed the code.

My guess is the user the code runs has no update privs. But does have 
create,


> 
>>
>> It isn't that big a deal really, I'm pretty good at proofreading the
>> articles before I post them but sometimes I'll spot a small typo or
>> something and want to go back and correct it (until now, lol).
>>
> 


-- 
"The great thing about Glasgow is that if there's a nuclear attack it'll 
look exactly the same afterwards."

Billy Connolly

[toc] | [prev] | [next] | [standalone]

#7008

On 11/8/2018 1:38 PM, The Natural Philosopher wrote:
> On 08/11/2018 18:01, Luuk wrote:
>> On 8-11-2018 12:48, super70s wrote:
>>> In article <5be2ecc4$0$32263$e4fe514c@news.xs4all.nl>,
>>>   Luuk <luuk@invalid.lan> wrote:
>>>
>>>> Are you using the correct statement to update this table?
>>>>
>>>> What is the exact error message that is given when you try to update an
>>>> article?
>>>
>>> The message in the "New Article" window says "Article Information Saved"
>>> as normal, however it refuses to accept the modification.
>>>
>>
>> OK, your application is telling you "the information is saved", but you
>> do not see the info in your database.
>>
>>> I'm afraid I don't have a lot of experience with this, in fact I had to
>>> hire someone to install the db so I apologize if I "offended anyone's
>>> senses."
>>
>> You indicate not to have experience with this db.
>>
>> How should we know what went wrong if we only see the descriptions of
>> wat want wrong, and do not see any logging, or any SQL statements?
>> (or, for the PHP part, any PHP-code)
> 
> I think that is the point...
> 
> he doesnt have access to admin level or indeed the code.
> 
> My guess is the user the code runs has no update privs. But does have 
> create,
>

Only an idiot would specify admin privileges like that. But you would.

> 
>>
>>>
>>> It isn't that big a deal really, I'm pretty good at proofreading the
>>> articles before I post them but sometimes I'll spot a small typo or
>>> something and want to go back and correct it (until now, lol).
>>>
>>
> 
> 




-- 
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#6998

On 06-Nov-2018, super70s wrote
(in article<super70s-64F973.15393306112018@reader.albasani.net>):

> 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?

Can you connect to the database with mysql? Can you update or remove records 
from tables? Can you export the database to a SQL file?

These are primitives that point to issues with the database. The web 
interface may be the underlaying problem. Until you isolate where the problem 
is, it's anyone's guess. It's like going to the dealership and saying "the 
car makes this weird sound when I go over 50".

Spend some more time isolating the issue and report back your findings.

-- 
DeeDee, don't press that button! DeeDee! NO! Dee...

[toc] | [prev] | [standalone]

Back to top | Article view | comp.databases.mysql

csiph-web