[xeagle]

Originally Posted by snowlion

This mod confict with Advanced Link Posting Option
https://vborg.vbsupport.ru/showthrea...d+link+posting
When saving a setting, I get white page

This is my log file content

Sun Aug 19 11:14:53 2012,400 [32443] WARN localFileLogger - PHP WARNING: [2] require_once(./includes/hooks/advlinkops/admin_options_processing.php) [<a href='function.require-once'>function.require-once</a>]: failed to open stream: No such file or directory on line 41 in file /home/lonely/public_html/forum/includes/adminfunctions_options.php(744) : eval()'d code. PHP 5.2.17 (Linux)
Sun Aug 19 11:16:19 2012,534 [1236] WARN localFileLogger - PHP WARNING: [2] require_once(./includes/hooks/advlinkops/admin_options_processing.php) [<a href='function.require-once'>function.require-once</a>]: failed to open stream: No such file or directory on line 41 in file /home/lonely/public_html/forum/includes/adminfunctions_options.php(744) : eval()'d code. PHP 5.2.17 (Linux)
Sun Aug 19 11:17:29 2012,727 [1935] WARN localFileLogger - PHP WARNING: [2] require_once(./includes/hooks/advlinkops/admin_options_processing.php) [<a href='function.require-once'>function.require-once</a>]: failed to open stream: No such file or directory on line 41 in file /home/lonely/public_html/forum/includes/adminfunctions_options.php(744) : eval()'d code. PHP 5.2.17 (Linux)
Sun Aug 19 11:24:40 2012,468 [6926] WARN localFileLogger - PHP WARNING: [2] require_once(./includes/hooks/advlinkops/admin_options_processing.php) [<a href='function.require-once'>function.require-once</a>]: failed to open stream: No such file or directory on line 41 in file /home/lonely/public_html/forum/includes/adminfunctions_options.php(744) : eval()'d code. PHP 5.2.17 (Linux)

These error messages don't actually mean that this mod is a cause of the conflict, etc. Probably that external mod "Advanced Link Posting Option" might conflict and be the one which generates these errors instead of vBSSO (vBSSO shows the errors that happen across all the vB modules). We will look through it anyway and check if we would be able to reproduce the similar issue using that external mod.

Please note that these are not the errors. These are the warnings that might appear in some of your custom modules.