SMF error - Unknown column 'owner_name' in 'field list' after upgrade

[Quinn]

User profiles error in SMF after Upgrade to CG 1.5.4...  previously working with 1.4.27

I get the following error in SMF 1.1.11 after I upgraded to coppermine 1.5.4 -

Code Select Expand


Unknown column 'owner_name' in 'field list'
File: /home/bs-raven/domains/forums.bs-raven.net/public_html/Sources/Profile.php
Line: 1463


Coppermine install: http://forums.bs-raven.net/galleries/
Bridging app install: http://forums.bs-raven.net/
Coppermine version: cpg1.5.4
Bridging app version: SMF 1.1.11
Test user account: tester / tester

BridgeManager settings:
Bridge app URL:  http://forums.bs-raven.net/
Relative path to your bridge app's config file:  ../
Cookie name or prefix:  SMFCookie554
Use post-based groups?: 0  

[Joachim Müller]

Coppermine doesn't have an impact on the bridge application - it doesn't modify the bridge apps's database tables nor the files. If you get an error in your bridging app, then it must be on the end of the bridging app. Out of the box, none of the bridging apps is "aware" of coppermine, so it should not query coppermine's database tables. Obviously, your copy of SMF is running a query against Coppermine's table, so you better review the edit you performed in the bridging app, which can't be supported by us, as we're not aware of the changes you applied. In other words: you appear to have edited http://forums.bs-raven.net/Sources/Profile.php; undo your edit there or do whatever it takes to make the error message go away.

[Quinn]

Thanks for the insight, it appears that the issue was related to a change in your tables for users as the Coppermine Userpics  1.0  mod was the culprit. I removed the user profile pics mod and SMF is happy again. 

[Joachim Müller]

For the benefit of others with similar issues you might want to post a link to the mod you're refering to. Please resolve your thread as suggested per board rules.

[Quinn]

http://custom.simplemachines.org/mods/index.php?mod=455 This mod has been in use since 2007 and is not compatible with your latest release. If I had more details on your end the author might be able to fix it to be compatible with CGQ 1.5.x. I will let the author know that it is broke on your end. So far I love the new 1.5.4 version... only the URL upload feature I used often isn't found, yet!

[Joachim Müller]

If I had more details on your end the author might be able to fix it to be compatible with CGQ 1.5.x.

What details do you need. The beauty of open source is that it's all there - just take a look at the code to figure out what the changes are.

only the URL upload feature I used often isn't found, yet!

It's not there - it has deliberately been removed:

URI upload removed
The URI upload feature has been removed from cpg1.4.x to cpg1.5.x, as it wasn't actually doing what many users thought that it would do: when using URI uploads people expected the file to remain at the URI that they entered into the upload form and not be transfered to the webspace where their Coppermine gallery resided on. Subsequently, they thought that they could safe webspace. This was a misconception and in fact just wishfull thinking: using URI uploads in cpg1.4.x, the file actually was uploaded to the Coppermine webspace no matter what.
Therefore, the actual feature "URI upload" was removed in cpg1.5.x. However (depending on the operating system of your client) you can (ab)use the regular http upload form to accomplish a similar thing in cpg1.5.x: when entering the URL of a file accepted by Coppermine into the http upload form, the file will get downloaded to your client's temporary folder and then a regular http upload from your client to your server will be performed. This is not actually a feature built into coppermine, but rather a feature of your OS/browser and therefore it goes unsupported. However, there is no action required when performing the upgrade - this paragraph is just meant to inform you that the feature was dropped.

[Quinn]

It's not there - it has deliberately been removed:

Too bad.. for those who understood the mechanics of the "feature" it was a great tool.   

[huafeihua116]

I got same error!

[onthepike]

While it's great that you searched the boards seeking a resolution to an issue you're having (or had, who can tell by the message you posted?), you should have followed other guidelines as well. Such as, starting your own thread and indicating whether or not you actually do continue to have the issue (or how you resolved it) and by posting a link to your Coppermine-driven gallery.

I got same error!

Is this a statement? A comment? A support request? What exactly do you want to happen now?

Start your own thread and include a link to your gallery.

[Joachim Müller]

Locking