Pp486 + VB3 Error Warning: array_merge

Geiri · January 11th, 2005, 02:20 PM

I am converting from phpbb2 to vb3.
Server is using PHP Version 5.0.0

I get this error in photopost User Index

Code:

Content visible to verified customers only.

This is on localserver so its not accessable

Interdit · January 11th, 2005, 05:30 PM

Hello,

I don't think Php 5.0 is ready for all applications, did you try with 4.3.10 ?

Later,
Interdit

Geiri · January 11th, 2005, 06:11 PM

No this was my first try.

Maby I have to downgrade?

:-/

Chuck S · January 11th, 2005, 11:53 PM

Also note your posting on the Photopost support forum yet your errors are with Vbulletin

I would if I where you make sure you have correctly switched from Phpbb to VB in Photopost

1. database points to vb3 now in config file as well as vb license number in there
2. in your database you changed settings table line 41 to vb3 as well as setting 83 to any vb3 table prefix
3. Edited the config-int.php file with the proper server paths to your vb forum as well as Photopost and photopost table config.

zatsu · January 27th, 2005, 04:56 PM

I am also getting this error.

It can be viewed at: http://test.mmopics.com/photopost/index.php

I tried various installs:

1) Fresh install with Photopost and vb3 using different databases
2) Fresh install with both using same database
3) Added vb3 to existing install of photopost

Each time I am getting the same error.

I have also verified all the config settings and license number, verified config-int.php

I have checked the settings table lines.

Still same error.

I do not recieve any errors on the forum itself. Just when I switch to the photopost directory.

My Configuration is:

Windows 2003 Server (all current)
IIS 6
PHP 5.0.3
VB 3.0.6
Photopost 4.8.6

I will continue to troubleshoot, but if anyone has had this issue and resolved, please post here.

Thank you

Note on the comment in regards to this being a VB3 error, this may be the case, but I purchased your product with the advertising that you integrate well with vb3.

This error only occurs when using your product.

I believe that any input your support staff can have in this matter would be most helpful.

Chuck S · February 25th, 2005, 09:02 AM

Still that error is specific to the VB code. Not Photopost code. I do see that on any system I have seen this on error reporting is usually set real high. You can alter the php.ini to this and see if it goes away

error_reporting = E_ALL & ~E_NOTICE & ~E_WARNING & ~E_CORE_WARNING & ~E_USER_WARNING & ~E_USER_NOTICE & ~E_COMPILE_WARNING

; Print out errors (as a part of the output). For production web sites,
; you're strongly encouraged to turn this feature off, and use error logging
; instead (see below). Keeping display_errors enabled on a production web site
; may reveal security information to end users, such as file paths on your Web
; server, your database schema or other information.
display_errors = Off

nexia · February 25th, 2005, 09:18 AM

... this bug is related to the vB integration, not vB itself...

in header-inc.php, add this in the begining of the vb3 integration:

Code:

Content visible to verified customers only.

... the array-merge call is requesting the entire list of arrays to be filled, and you don't have all of the them yet... creating them will stop the error.

(it's never good to suggest to edit php.ini when the problem is error reporting...)

Chuck S · February 25th, 2005, 11:01 AM

First off your talking about the beta header include and you can report this there if you wish. I cant comment specifically what on php 5 causes this.

Second I think your wrong about php.ini scope as the php.ini file tells you this and even tells you what I have stated. display errors must always be off and php states this.

; - error_reporting = E_ALL [Code Cleanliness, Security(?)]
; By default, PHP surpresses errors of type E_NOTICE. These error messages
; are emitted for non-critical errors, but that could be a symptom of a bigger
; problem. Most notably, this will cause error messages about the use
; of uninitialized variables to be displayed.

Basically if you have your error reporting set so high that empty values are reported there is nothing you can do or we can do.

Basically arrays or variables are empty till brought into use in php so do as you wish.

I am just posting a possible option that might get rid of this error

nexia · February 25th, 2005, 12:33 PM

better action for error reports. on top of your files, write this:

Code:

Content visible to verified customers only.

you will then deactivate the entire Error_Reporting system without having to re-write your php.ini ...

and the problem with array_merge is recurent, so even if you already know that a array is empty, mergin an empty/not created array with another will cause an error... deactivating the error system is good, but not correct the bug anyway...

oh, and yes, it's a PHP5 error, as display_errors is always set to TRUE by default... webservers have to deactivate it... most don't, for security!

Sir_Varadero · February 27th, 2005, 07:01 PM

Quote:

Originally Posted by nexia

... this bug is related to the vB integration, not vB itself...

in header-inc.php, add this in the begining of the vb3 integration:

Code:

Content visible to verified customers only.

... the array-merge call is requesting the entire list of arrays to be filled, and you don't have all of the them yet... creating them will stop the error.

(it's never good to suggest to edit php.ini when the problem is error reporting...)

I did edit the php.ini and tried the option to turn off the display errors - but the problem was still present! (running on WinXP, Apache 2.0.52, PHP 5.0.3 and MySQL 4.1.10)

Your hint about creating those arrays solved the problem - thanks a lot for the help!