Issue: Errors when rebuilding namespaces: Cannot use a scalar value as an array

Issue Tools
- View Changes

July 20, 2010 3:13 PM
Alfa1

Distinguished Member
Errors when rebuilding namespaces: Cannot use a scalar value as an array

In relation to this thread:
http://www.vaultwiki.org/threads/4707/

When rebuilding any namespace, I get this error:

Code:

Warning: Cannot use a scalar value as an array in [path]/admincp/vaultwiki_namespace.php on line 479 Warning: array_keys() [function.array-keys]: The first argument should be an array in [path]/includes/adminfunctions_options.php on line 422 Warning: Invalid argument supplied for foreach() in [path]/includes/adminfunctions_options.php on line 422

The errors are a conflict with: Product : AWCoding- Back-End
This is the back end of the AWCoding Donation System. Version 3.0.8

AWCoding adds values to the object, but in no shape or form does it change it to a string.

The plugin in that affects Vaulwiki is the init_startup:

include(DIR.'/awcoding/plugins/awc.php');

Issue Details

Issue Number 1814

Issue Type Bug

Project VaultWiki 3.x Series

Category Namespaces

Status Fixed

Priority 5 - Minor Bugs / Small Tweaks

Affected Version 3.0.1

Fixed Version 3.0.2

Milestone VaultWiki 3.0.5

Software DependencyAny

Users able to reproduce bug 0

Users unable to reproduce bug 0

Attachments 0

Assigned Users (none)

Tags (none)

July 20, 2010 5:28 PM

pegasus

VaultWiki Team

$settings as used by AWC is a MySQL resource. At least according to Donations lite - I cannot find the back-end itself anywhere - the variable is not destroyed after use.

As long as this was the problem, it's an easy compatibility fix for the next build.

Reply
July 22, 2010 4:38 PM
Alfa1

Distinguished Member
Will the next build work on 3.8.x ?

Considering the code within plugin init_start: AWC asked me to post this:

Originally Posted by AWC

Code:

$vbversion=substr($vbulletin->options['templateversion'],0,1); $settings=$vbulletin->db->query_read("SELECT varname,value FROM ".TABLE_PREFIX."awc_settings"); while ($setting=$vbulletin->db->fetch_array($settings)){ $vbulletin->options[$setting['varname']]=$setting['value']; } $awc_base=$vbulletin->options['awc_base'];

I presume I am overriding his $settings value. Which should be software specific not to conflict with any other modification. New v4 changes it to $awc_settings_sql and $awc_setting. So again new version won't conflict and he needs to change it as well as both him and I overlook that simple thing.
The issue has to be $settings/$setting. Needs to be software specific. $awc_settings/$awc_setting
where $vw_settings/$vw_setting should be his.
Reply
July 22, 2010 5:33 PM

pegasus

VaultWiki Team

Yes, the next build will still work on 3.8.x.

The issue he mentions is not exactly what was occurring, but some new checks should prevent any other potential conflicts in the future.

Reply
July 22, 2010 7:06 PM

Alfa1

Distinguished Member

Thanks for the swift response!

Reply

+ Reply

All times are GMT -4. The time now is 2:50 PM.

This site uses cookies to help personalize content, to tailor your experience, and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.

Learn more… Accept Remind me later

Welcome to VaultWiki.org, home of the wiki add-on for vBulletin and XenForo!

Issue: Errors when rebuilding namespaces: Cannot use a scalar value as an array

Issue Tools