This may be a bug (given other theming posts here) or it could be an issue that has a workaround.

I have a site-wide default theme and a specific custom theme for showing large Views tables. I use the Page Theme module to assign that special custom theme on specific pages, in this case specifically to the primary views host table and a small views table the Megarow calls and displays in-situ. However, the Megarow, once opened, shows a combination of site theme and the theme assigned to it and breaks the host view theme. The net result is that submit buttons revert to the site style and all text boxes (for editable fields) in the entire view and Megarow get assigned a tiny height (or padding is too big) resulting in narrow slits for editing text boxes.

Tracking this down in Chrome's inspect/CSS tools, I can't find the root cause as there doesn't seem to be a clear CSS directive that's doing this. It looks like it may be a computed CSS result.

Is there a way to override the theme the Megarow uses so that I can force a correction? I could use JQuery to force the height of my input fields, but that would be a dirty hack that doesn't address the underlying issue.

Any thoughts/suggestions? Any assistance is very welcome as this issue is making my project unusable.

CommentFileSizeAuthor
#2 views_megarow-2884743-2.patch932 bytesimyaro

Comments

hondaman900 created an issue. See original summary.

imyaro’s picture

Status: Active » Needs review
StatusFileSize
new932 bytes

Hello,
I have met the same issue.
Seems problem in the theme callback when we have a language prefix.

andrii momotov’s picture

Status: Needs review » Closed (outdated)

D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7. All D7-related issues are marked as outdated in a bunch.

Everyone can apply the patch above (not tested by the maintainers) to their D7 projects.
If the issue remains relevant for D10+ versions, merge requests with proposed solutions for a new module version (D10+) are welcome in a new follow-up issue.

Thanks!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.