kiwi3685

Sorry – forgot your other question:

<<Are you running a Windows server by any chance?>>

No, just a standard Unix server. Nothing unusual about the set up as far as I’m aware.

Thanks, that certainly helped. Just a couple of minor corrections were required:

Your new code for line 806 is slightly wrong (missing two occurrences of $this->). Should be:
$crumbs = array(‘settings[‘slug’]).'” class=”incsub_wiki_crumbs”>’.( isset( $this->settings[‘wiki_name’] ) ? $this->settings[‘wiki_name’] : ” ).’‘);

Your new code for line 833 is an (accidental) copy of your new code for line 832. It should be:
‘order’ => ( isset( $this->settings[‘sub_wiki_order’] ) ? $this->settings[‘sub_wiki_order’] : ” ),

With these two changes all the original errors were cleared.

Thanks for the help.

I can see that the problem is in lines 783, 784 of bug-library.php. They hard-codes the suffix “.jpg” for every attachment.

Is there any reason why this is necessary?

Can I simply remove the hard-coded suffix?

Is there any likelihood of further support response on this issue?

I have now been through and deleted every plugin, one-by-one. None made any difference to the error messages.

I tried adding debug, but that gave no further information.

However I have found more similar errors that might be significant:

If I add a sub-wiki I get an error breadcrumbs:
Undefined index: breadcrumbs_in_title in /home/onenamek/public_html/wp/wp-content/plugins/wordpress-wiki-plugin/wiki.php on line 322

Also, if I make any changes to my site menu it generates another series of identical errors:
Undefined index: post_type in /home/onenamek/public_html/wp/wp-content/plugins/wordpress-wiki-plugin/wiki.php on line 1933

Looking at all the errors reported, are these not all parts of the code related to the pro version, and not available in the Lite version?

If so, how have I managed to end up with them. I have only ever (last week) downloaded the lite version.

To answer your final question – yes apart from filling the screen with error messages the plugin works OK. Whether it will provide what we need I will only be able to judge if it ever becomes usable. We might be interested in using the Pro version, but not if this Lite one can’t be installed in our situation.

David

Error messages are as per my post above (front end). There are no error messages in the back end (assuming by that you mean the WP admin area?

WordPress version is 4.0
PHP version is 5.3.28

The site (actually the dev. site for a large main site) has 31 active plugins. Any suggestions what type of plugin to start deactivating? I would prefer to leave that as a last resort, because if it is a conflict with a plugin I am more likely to abandon wordpress-wiki than any other.

An explanation for where the “missing” index’s should be coming from might help me diagnose the issue.

Thanks. I suspected that might be the case. But it doesn’t seem to be happening (though it does with ‘normal’ comments), so I will have to dig further into what I have set wrong.

Very happy to report that this is now working perfectly. Thanks.

Please try it out if you can and let me know if it does the trick.

Thanks. I’ll try to test this tomorrow.

I uploaded my version of theme-my-login-custom.php yesterday to replace the one deleted by the update to 6.3.10, but today I get another update reminder because the system thinks I am still on 6.3.9! It seems I need to first change the version number of that file before I upload it!! All for a file that I haven’t changed.

PLEASE, can this file be excluded from the update process????

You will find the instructions here: https://www.jfarthing.com/development/theme-my-login/adding-extra-registration-fields/

Just updated to TML 6.3.10 and this happened again. Fortunately I keep a backup of the file, but why does an update need to delete this file?

Thanks Mike. I appreciate the help and the great plugin.

Not only did I need the correct code, but I was putting it in the wrong file ?? All good now though.