PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'b.parent' in 'field list': SELECT b.parent AS parent FROM {browscap} b GROUP BY parent ORDER BY parent ASC; Array ( ) ב-mobile_tools_browscap_get_browscap_parents() (שורה 139 מ-/home/meytarim/public_html/site12/sites/all/modules/mobile_tools/mobile_tools_browscap/mobile_tools_browscap.module)

why cant i update or and a new device group to mobile tools?

tnx

Comments

Drave Robber’s picture

You need to apply the patch in #1713570: Change Browscap database schema to match the columns defined in the default XML schema from the browscap data.
This information could be found in /mobile_tools_browscap/README.txt, by the way.

Remarks re drupal.org workflow:

  • please assign an issue to yourself only when you plan to write a patch or do other work on the issue;
  • please set an issue to 'needs review' only when there is something to review (e.g., a patch). Thank you!
Drave Robber’s picture

Component: User interface » Code
Assigned: yoya.negba » Unassigned
Status: Needs review » Active

(this is probably 'Closed (works as designed)' but I'll leave the decision to the maintainers :)

aptorian’s picture

Status: Active » Closed (works as designed)
ñull’s picture

Category: Support request » Feature request
Issue summary: View changes
Status: Closed (works as designed) » Active

If mobile tools to function correctly depends on this patched code, then I would think the same rules apply as library dependencies where a warning appears in the Status page and often even a message in the help region and on the command line when using drush.

Especially when you install with drush, dependency modules like browsercap are installed on-the-fly and it is not very obvious that you should patch something, when there is no warning displayed.

ñull’s picture

Category: Feature request » Bug report

I changed to bug status because numerous user reports contradict if the offered patch solutions work for them. There is no agreement nor an accepted dev version. Until then this issue should remain in active bug status. Functionality remains broken until there is working (dev) release of the depending module.

shyam kumar kunkala’s picture

Assigned: Unassigned » shyam kumar kunkala

Working on this issue

shyam kumar kunkala’s picture

Status: Active » Needs review
StatusFileSize
new380 bytes

I am able to reproduce the issue.It's a fatal error and fixed the issue. I am attaching the patch.

rajeev_drupal’s picture

Status: Needs review » Reviewed & tested by the community

Fixes works for me....

shyam kumar kunkala’s picture

Project: Mobile Tools » Browscap
Version: 7.x-3.x-dev » 8.x-1.x-dev
shyam kumar kunkala’s picture

Version: 8.x-1.x-dev » 7.x-2.1
greggles’s picture

Status: Reviewed & tested by the community » Closed (duplicate)

There's no patch here so it's not RTBC. I think it's a duplicate of #1713570: Change Browscap database schema to match the columns defined in the default XML schema from the browscap data. People interested in the topic should work on that issue.