markusk

seen this?
https://github.com/moeishaa/jglance
https://moewashere.com/jglance/
(hurray for badly SEOed pages..)

what i suspected. probably cropping is the only way to get around this..

so you did write this yourself? this isn’t a thirdparty-lib? isn’t there any?..

no need to be snippy wott, as mentioned above – i didn’t have time to investigate the issue further, and i don’t see much sense in providing an incomplete bug report..

back then i gave all users of the affected site admin-rights to work around the issue, and actually didn’t ask for any support. whenever i get to work on this again (it’s that kind of non-profit/community-thingy) i’ll sure report the way you wish.

thanks for investigating on this, still didn’t find time to do so..

didn’t think of a user-permission-issue at first, but indeed it might be it..

it seems to be the plugin not supporting multisite properly, i.e. it doesn’t integrate itself in newly created blogs. strangely it works for me in the first “sub-blog” i created, but not in any other – can u confirm this as well?
didn’t have time so far to find out how/where to report bugs for this, as it doesn’t seem as if this place is one that the author(s) monitor(s).. ??

i know that the codex-pages are work in progress and actually a wiki (already corrected it myself).

may i make a suggestion for this paragraph:
now that all is nicely interfaced via the administration-panel (guess this wasn’t the case when it was written) i and probably many other useres don’t really care about the location of plugins in the filesystem – so i think this should be written a lot more “ui-centric”, keeping the parts about the file locations just as a sidenote..

but..

Network Plugins: WordPress Plugins that are also stored in the plugins directory can be activated across the entire network by the super admin. Once ‘Network Activated’ plugins will become active in all sites. ‘Network Activated’ plugins will hide their activate/deactivate menu options to individual site administrators. Only super admin can deactivate a ‘Network Activated’ plugin on a site by site basis.

according to this – i (as networkadmin) *should* see (and be able to activate/deactivate) sitewide enabled plugins on a “site by site basis” – is this wrong?

[what is esp. confusing in this codex-page is the inconsistency of naming.. once it says “site”, then it’s “blog” again, all referring to the same thing..]

ok – then we’re getting somewhere, and i totally misunderstood the concept – i didn’t really grasp it that way from this https://codex.www.ads-software.com/Create_A_Network#WordPress_Plugins (and didn’t find any other place dealing with it)

additionally it seems that some of the plugins i installed aren’t quite ready for this – which led to this confusion.. (namely sitewide activated plugins weren’t showing it’s settings in later created blogs)

thanks,
markus.

i’m afraid you got my problem wrong..

first off, the plugin-menu for admins *is* activated, but it’s empty for “normal” admins (although there are multiple plugins activated sitewide).

only i as network-admin can see one plugin in these blog-specific menu – it’s akismet. this is disabled site-wide (so it makes sense that normal admins can’t see it).

but again, there are multiple other plugins enabled site-wide, but neither i as network-admin, nor any other “normal” admin can see those in the blog-menus.

thanks,
markus.

been a typo in codex page – and silly me just looked at that.. said vhostS.conf in multiple places whereas it should be vhost.conf. already corrected it.

assuming u mean in dns-settings – definitly not..

*.mine.net CNAME mine.net

vhosts.conf also exists with correct:
ServerAlias *.mine.net

(and of course the wp-installation *does* properly work under mine.net)