My guess would be a conflict with another plugin or something is not letting mDocs javascript to load. Try disabling plugins to see if the problem goes away.
If it is a plugin let me know which one and I can see if I can find a work around.
Hi,
I have installed a fresh wordpress and uploaded the plugin still the same issue.
The fresh WordPress install had not been tempered with, so i guess it is your plugin that has some issues.
Do you see any javascript errors in the development console?
Yeah,
It says;
Uncaught SyntaxError: Unexpected token ILLEGAL file name admin.php line 445;
I have looked at that line and found the below;
jQuery( document ).ready(function() {
mdocs_admin(‘http://localhost/chirag/wp-content/plugins/memphis-documents-library/’, ‘C:\xampp\htdocs\chirag/’);
});
yeah that is a problem, don’t know what the error means yet but something is not loading properly.
Ill keep looking.
I am also looking but in the mean time you can look in the below link;
http://stackoverflow.com/questions/12719859/no-visible-cause-for-unexpected-token-illegal
I really hope i/we can figure this out. I need to use this plugin for a project that is almost due.
Hi there. I have the exact same error, and I noticed that joeynimu was also using XAMPP.
So just to be sure I tried a different apache server (EasyPHP) and sure enough Memphis now works properly.
I have no idea what the issue is, but it definitely seems to stem from XAMPP.
thanks for the heads up, I’ll take a look into this issue see if I can find a solution.
one solution that i saw for this was to echo the jQuery( document ).ready(function() {
if you want to try this open mdocs-settings.php line 458 and line 470:
?>
<script type="application/x-javascript">
jQuery( document ).ready(function() {
mdocs_wp('<?php echo MDOC_URL; ?>', '<?php echo ABSPATH; ?>');
});
</script>
<?php
and change it to this
echo
'<script type="application/x-javascript">
jQuery( document ).ready(function() {
mdocs_wp("'.MDOC_URL.'", "'.ABSPATH.'");
});
</script>';
No activity closing case.
Still facing the same problem..even after changing the code as mentioned above. I think this problem is only with WP 4.3.1..