I get three 3 errors that prevent adding products

[fantiques.com]

( I've previously posted this problem as an additional reply to other posts
rather than starting another thread; sorry if this post appears redundant)

Oh well, here goes:

I've tried every remedy posted so far, without resolve.

I'm running Prestashop 1.6.0.9 on a Apache host server.

I get three 3 errors that prevent adding products:

*    This name field is required at least in English (English)
*    Products must be in at least one category.
*    This product must be in the default category.

It's not only impossible to upload a product, but the program
deletes everything you've typed in while it tells you there's an error.

The error reporting module returns this message when entering the
product editing module, and/or every attempt to edit within that module:

=====
Warning on line 170 in file /home/fantiques/shopcart/modules/gamification/gamification.php
[2] file_put_contents(/home/fantiques/shopcart/modules/gamification/views/css/advice-1.6.0.9_324.css)

[<a href='function.file-put-contents'>function.file-put-contents</a>]: failed to open stream: Permission denied
=====

How do I fix this?

Thanks,

John
fantiques.com/shopcart

 

[El Patron]

check that back office domain name (www or not www) is same as what is defined in prefrences-->seo & urls-->shop  domain 

 

if shop domain has www, then make sure to access bo with www, or vice versa...

 

I had same 'exact' issue, this resolved it.

[El Patron]

for review, this link:

 

https://github.com/PrestaShop/PrestaShop/commit/5cae06908714bbb5f45f9c9bf98d7f1f158d3f81

 

try this:

http://screencast.com/t/CYZ2mgm7uln

[fantiques.com]

I had tried that remedy, but just tried it again anyway... No luck.

Since the file can be accessed, it doesn't appear to me

to be a permission problem, although.......

The most frustrating thing about this problem, is that it is
intermittent. I managed to get 9 products listed since starting
to run this version, with a terrible fight with each one listed.
The problem seems to have gotten worse and is now more
contunuous.

The "error report" posted in my first post is what concerns me:
==
Warning on line 170 in file /home/fantiques/shopcart/modules/gamification/gamification.php
[2] file_put_contents(/home/fantiques/shopcart/modules/gamification/views/css/advice-1.6.0.9_324.css)
[<a href='function.file-put-contents'>function.file-put-contents</a>]: failed to open stream: Permission denied
==
I'm obviously not a programmer (although I managed to build
fantiques back in the 90s), and dealing with multiple files to
generate one html page is a bit mind-boggling at best.

I would like to know how that above "warning" can be resolved.

Thanks for the input!

John
 

[fantiques.com]

I tried Github files, and ended up with the same probem that the
original poster remained to have.

I may try the github files again, but I'm putting an awful lot of time
into all the repeat attempts. Most "remedies" have not resolved this
problem for others experiencing this problem, adding to the frustration
of seeing "problem resolved" and "thread closed", when the problem
remains.

When so many users are reporting the exact same errors when
attempting to add a product, it seems to me that it's a generic problem
and something fairly simple just need to be addressed.

While true, that: "there's no such thing as a little bug", I seriously do
not think it is a "bug", but merely an oversight. It isn't crashing the
program, it's just sending the wrong message for a specific part
of the program.....

Ajax related?

 

(by the way, I don't have the ability to change the server settings as

indicated in your post; that option is not provided here)

Thanks,

John
 

Edited November 1, 2014 by fantiques.com (see edit history)

[fantiques.com]

Update:

The error:   
Warning on line 170 in file /home/fantiques/shopcart/modules/gamification/gamification.php
[2] file_put_contents(/home/fantiques/shopcart/modules/gamification/views/css/advice-1.6.0.9_324.css)
[<a href='function.file-put-contents'>function.file-put-contents</a>]: failed to open stream: Permission denied

Has been resolved by changing file permissions in the /shopcart/modules/gamification/views
/advice-1.6.0.9_324.css (etc) files to 664. Apparently group writing is necesssary.

The problem of not being able to add products due to the same three errors, continues.

Re:
*    This name field is required at least in English (English)
*    Products must be in at least one category.
*    This product must be in the default category.

I hate to give up, but I can't do a thing if I can't add products and I've tried every "fix"
out there so far (as have others experiencing the same problem).

The github files did not resolve the problem. In fact, for me, it added a problem of the
save buttons being greyed out as if having been pushed, and the "save" indicator spinning
continuously. (nothing was saved, however).

Does anyone have a resolve for this problem? Is there anything else I can do to locate what's
going wrong? Is there a way to set the program to ignore the language and category errors?

What's wrong with my version 1.6.0.9?

 

[El Patron]

you said "Has been resolved by changing file permissions in the /shopcart/modules/gamification/views
/advice-1.6.0.9_324.css (etc) files to 664. Apparently group writing is necesssary."

 

what concerns me about this statement is what other files may have similar/same issue?

 

When we talk about group file ownership, all folders/files should be owned by 'domain' they are running in.  Real issues can be created depending on how one moves their ps files to remote, ftp is 'only' safe way of doing this,  using ftp account for 'that' domain.  I've seen some that say will zip and then unzip to remote, this will more often than not create group ownership incorrectly.

 

also...if we turn off mod_security in back office, I'd go one step further and disable on hosting...(recreate .htaccess file)...

[fantiques.com]

you said "Has been resolved by changing file permissions in the /shopcart/modules/gamification/views

/advice-1.6.0.9_324.css (etc) files to 664. Apparently group writing is necesssary."

 

what concerns me about this statement is what other files may have similar/same issue?

 

When we talk about group file ownership, all folders/files should be owned by 'domain' they are running in.  Real issues can be created depending on how one moves their ps files to remote, ftp is 'only' safe way of doing this,  using ftp account for 'that' domain.  I've seen some that say will zip and then unzip to remote, this will more often than not create group ownership incorrectly.

 

also...if we turn off mod_security in back office, I'd go one step further and disable on hosting...(recreate .htaccess file)...

I use FTP for all file transfers; I never trusted the "auto-install" operations.

 

Since the addition of products had worked intermittently, I had little reason

to question the permission settings. But I had to have the hosting company

techs reset the PHP server settings, since the program was reporting errors

regarding PHP server limitations. The problem of not being able to add products

had gotten much worse since then.......

 

It would be handy to have a list of the recommended permissions for directories and files

for all of Prestashop. If one already exists, the url should be posted, or the information

included with the download.

 

Thanks for your input, it's appreciated!

 

John

 

[fantiques.com]

Update:

associations tab
Attempt to save or change error:
This link_rewrite field is required at least in English (English)

language tab
Pop-up Error:
Warning on line 1925 in file /home/fantiques/shopcart/classes/Tools.php
[2] fopen(/home/fantiques/shopcart/.htaccess) [<a href='function.fopen'>function.fopen</a>]: failed to open stream: Permission denied


The Prestashop (root) .htaccess file is 73 lines long, is that normal,
or could this be the source of problems with the inability to add products?

Temporarily disabling the htaccess file allowed a change to the product, but
a new htaccess file (25 lines long) was generated and added new problems, while also
making it again impossible to add or change a product and producing the same errors.
-----
# ~~start~~ Do not remove this comment, Prestashop will keep automatically the code outside this comment when .htaccess will be generated again
# .htaccess automatically generated by PrestaShop e-commerce open-source solution
# http://www.prestashop.com - http://www.prestashop.com/forums
-----

I ain't a young guy..... this is making me even older.
 

[El Patron]

I hear you pain, I'm probably oldest moderator...we try to help and sometimes we just hold each others hand...

 

now I think we need PrestaShop help.

 

please open a bug report here:

http://forge.prestashop.com/

 

please post the bug report link back here for others to follow/vote up/comment...

 

thanks,, el

[fantiques.com]

The "bug report" is now active:

http://forge.prestashop.com/browse/PSCSX-3796

 

Hopefully we'll have a final remedy!

 

I'm a die-hard and hate to toss in the towel; just stubborn, perhaps?

(is that a sign of an aspiring programmer? Stubbornness?)

 

I had a choice of working out an easier way to: upload products to our

present HTML/cgi website, add an easier method for a customer to

purchase products, and a way to include dynamic USPS postage

schedules for the specific product. Difficult to do with a simple HTML

site, but perhaps even more difficult with a css/php/tpl/html site, ehh?

 

Let us prey…. (/humor)

 

Thanks el...

 

John

Edited November 4, 2014 by fantiques.com (see edit history)

[asgllccb]

I was getting the first error and learned that I had some characters that it would not accept (the + sign).  I did straight numbers and letters and it resolved.  Don't know if this will help or not.

[fantiques.com]

I remember your post!

 

Thanks for the input!

 

Tried that, but it didn't work for me.

 

This product problem has been around awhile, and from

what I've read, remains to be around to this day (obviously).

 

It doesn't effect every installation, and can be intermittent

making it very elusive....

 

Can you still add and modify products?

 

John

[asgllccb]

Yes, but I am on 1.6.0.8. Don't trust .9 yet, I feel like it's too new.  I did about 3-4 months of testing on a test wamp server before updating my live one.  I still had a few surprises on the live site update that I did not run into on the test and seems like everything's resolved so far but 1 minor problem unrelated to this.  Yes, this has been around for a while. I feel like I lucked out on my solution finding it on the 1.5 topic.  Sorry it didn't work for you.  I'm at a loss otherwise.  Good luck.

[fantiques.com]

Some helpful information for those (like myself) that are struggling to get version 1.6.0.9 to list products.

 

This is what has helped (for me):

 

Go to your: Dashboard / advanced parameters / configuration information

And scroll to: “Check your configuration”

 

It will list any files or directories with problems with permissions, etc.

 

Set permissions to all files and directories to 775 using a suitable FTP program (such as FileZilla).

 

That should help clear some errors.

 

I changed the .htaccess file name in the Prestashop root directory to taccess (no period) rather than delete it totally. Disabling it provides a way to restore it quickly if necessary. With any luck, prestashop will not replace that .htaccess file as it normally does (it, so far for me, has not been replaced).

 

Adding a new product may still produce the error reports (not in category, language not set, etc), but you might find that it has saved the addition anyway. I saved the product after using only the basic “information” tab, then edited the balance of the information after it was saved. Same error reports, but the item was listed and appears in the proper category with the proper shipping, image, cost, etc.

 

Adding products takes much too, too, too long using these alternative methods and can be very frustrating, but until a permanent and proper re-write of the Prestashop 1.6.0.9 script is accomplished (sans bugs), this may take you through the night.

 

(maybe)

 

John

[El Patron]

...I'm pretty sure there will be no 1609 fix, you will be looking at upgrade to 161.x...might want to prepare for that upgrade...by creating running prod test copy.....just saying...

[fantiques.com]

...I'm pretty sure there will be no 1609 fix, you will be looking at upgrade to 161.x...might want to prepare for that upgrade...by creating running prod test copy.....just saying...

You do realize you’re making an old grown man cry, right?

 

I suppose creating a csv file of products wouldn’t be a bad idea… But what about themes, and modifications to themes, etc? Is there a safe way to backup the mess so a revision/new version won’t result in a ton of work?

 

There should be a “sticky” explaining how to save the basics to use after an upgrade.

 

(It might be easier to add a product upload form and purchase order form to my present (and equally as old) HTML website. My efforts are to make things easier for my [spam-filter] and her Ipad…. after 50+ years, it’s too late for a pre-nup….)

 

So far the temporary work-arounds listed above have enabled the addition of products. The last addition took about ½ hour however…. I’m still attempting to resolve the “errors” issue… I’m hoping the scripting guys will get it figured out the right way… You can only fix things with duct tape temporarily.

 

Thanks for the “head’s up”, el,

 

John

[El Patron]

yes best to 'be prepared' I saw (final solution)  to be incorporated into 1.6 final...did not look like retrofit to earlier 1.6 (so here we are holding hands).  

[fantiques.com]

The inability to add products due to the three errors mentioned at the start of this thread remains. After each change and/or deletion of an .htaccess file the problem temporarily disappeared, but the original problem would return once again anyway.

 

This “bug” has been marked as “solved” and the report closed, with the note that the “fix” for this will be included in the new version release.

http://forge.prestashop.com/browse/PSCSX-3796

 

The continual re-write of the Prestashop root .htaccess file possibly being responsible for the inability of various other files to be written to, has not been addressed, and is being considered as an individual host server (file permission) problem.

 

If the Apache server has to write to this file and so many are having a problem due to their server’s inability to write to it, why not change the requirement for having that file to begin with and solve the problem for all users?

 

Anyone experiencing this problem should voice their situation by generating a “bug report”. Each previous report one has been marked as closed, but it should be made known that this problem is serious and needs more immediate action.

 

If no immediate action is possible, then at least tell those that are knocking themselves out, to stop trying to fix what can’t be fixed without a total re-write.

 

It’s a lesson in futility; frustration with a capital “F”.

 

It’s free, however… For that, I’m thankful.

 

John

Edited November 5, 2014 by fantiques.com (see edit history)