refact(zopeutil): Made error msg more descriptive

[cmeier76]

This PR tries to improve the feedback in ZMI if errors occur in custom code. It replaces the internal representation <Products.zms.zopeutil.MissingArtefactProxy object at 0x113a57890> by a more descriptive error messages for broken ExternalMethods in ZMSMetaobjManager.

I cannot fully assess the impact of changing the try/except-handling in zopeutil, as I do not understand the previous changes referenced below. Furthermore, other ZMS*Managers with ExternalMethod support may affected and must be addressed.

References:

• Installation-Fixes zms.unibe#42 (comment)
• fixed addExternalMethod #354
• handle missing ext methods in repomanager #160

[drfho]

good idea to monotonize it.
I removed the extra-info in case of missing artefact and prepended that info to the error-info block within the textarea. Moreover there the warning-icon appears as an eye-catcher:

[drfho]

LTGM, ready for merge

[drfho]

Code-Errors in Meta-Cmds

Following this approach I tried to fit error messages of meta-cmds as well: it is tricky, because ExtMethod (in contrast to PyScript or ZPT) dont provide syntax validation by Zope. Until now a wrong py-syntax (e.g. import of not-installed module) just broke saving and thus the Zope object (the pointer to the external method) was not deleted - by chance. If the code was once broken, you could not repair it via ZMI.
I added a helper function for checking the py-syntax (incl. imports): zopeutil.addExternalMethod.upfront_syntax_check(data)
to avoid the ExtMethod-reloading/recompiling in case of code-errors.
Now its possiible to repair a defect cmd in ZMI instead of e.g. unloading via repo-manager.

ZMS/Products/zms/zopeutil.py

Lines 259 to 282 in 0a8b3ef

	def upfront_syntax_check(data):
	import ast
	import importlib.util
	try:
	tree = ast.parse(data, filename=filepath)
	except SyntaxError as e:
	standard.writeError(container, "[SyntaxError in External Method '%s']: %s"%(id, str(e)))
	return False
	missing = []
	for node in ast.walk(tree):
	if isinstance(node, ast.Import):
	names = [alias.name for alias in node.names]
	elif isinstance(node, ast.ImportFrom):
	names = [node.module] if node.module else []
	else:
	continue
	for name in names:
	top = name.split('.')[0]
	if importlib.util.find_spec(top) is None:
	missing.append(name)
	if missing:
	standard.writeError(container, "[Missing imports in External Method '%s']: %s"%(id, ', '.join(missing)))
	return False
	return True

[zmsdev]

LGTM

[cmeier76]

@drfho Now I'm missing the hint from the thrown exception that I introduced earlier to locate the problem in the code - but maybe the general error message will be sufficient

[cmeier76]

BTW. For zms.unibe.agenda.OutlookConnector I introduced in zms.unibe-2026.2.0 a handling of missing MS Graph API support and disabling if not available