kmtrent

Working perfectly now! Thank you!

Taking the .htaccess file out does not change the issue. I am considering re-building everything…can’t see any other way at this point.

I may check with hosting provider to see if there is anything that I’m missing.

The WordPress update to 4.4.2 did not change anything.

Ok, I used the checkout/checkin functions to clear the hold. Sorry, I should have thought of that!

Ability to release a hold would be a feature request to add for future updates. ??

Since the latest WordPress update, we are also unable to change entry creator. The options are only showing administrator roles. We are able to edit the actual entry though. Trying to figure this out too…

Sorry for the delay in response on my end. When I click on Upload New Image, nothing happens. I do see the button, but it is not linked to anything. There are no errors…just click and nothing happens.

Thanks for info about button in event description. I thought that might be the thing…

Let me know if you have any thoughts on how to resolve the sponsor Upload New Image issue.

We use WP-Client for a front end user plugin. They provide shortcodes which allow a user to edit their profile when logged in and give access to special pages that a user is assigned.

I am not concerned about giving access to profile edits as much as access to current holds and item due dates.

We will try the backend dashboard for now, but I would love to see a front end shortcode that links to a user’s login. This simplifies a user’s experience on the website.

Thank you for responding so quickly! I do love the simplicity of the plugin.

Thank you! You have been great to get right back to me about my concerns. I will keep troubleshooting and let you know if I discover the issue. We are not multisite, but we do use lots of plugins and hefty security.

I do have to keep all the input fields clear of apostrophes when adding an item. Also, a dash has presented an issue in the title field.

I found how to open up the backend for the user, and a patron can access all the holds/checkouts/profile there.

Would like to have a way to keep them from another step for viewing their library account though. Would appreciate any suggestions or helps or future support for a front end option!

I have found that the issues with adding items was how my site dealt with the punctuation inside the titles or descriptions. Since these are rendered as urls, the apostrophes, backslashes, and even periods present a problem. My security walls also see these markings as hacking attempts.

But, I am adding items now though! Still getting the AJAX error: 0 with the Amazon search, and I am simply not using this option.

Yes, I have acquired and inputted all the Amazon information.

1. My hosting lists the platfom type as Debian. Is this what you need?
2. Single
3. Chrome, MS-Windows

I am still experiencing all the issues, but occasionally the add item button will work. I have to leave out all apostrophes and hold my head just right (haha).

Here’s a new php error:
[06-Apr-2014 23:31:08 UTC] PHP Fatal error: Call to a member function show_errors() on a non-object in /wp-content/plugins/weblibrarian/includes/database_code.php on line 865

Sorry for all the posts. Thinking maybe my process will help identify a way to help.

well…it let me add one item…now I’m back to same error…

Turned on the Debug database setting and made database. This helped the ADD ITEM issue, but I am still getting the same error for Amazon.com search option.

Here’s a copy of my PHP error log:
PHP Warning: Invalid argument supplied for foreach() in l/wp-content/plugins/weblibrarian/includes/WEBLIB_Statistics_Admin.php on line 145
[06-Apr-2014 21:45:32 UTC] PHP Warning: Invalid argument supplied for foreach() in /wp-content/plugins/weblibrarian/includes/WEBLIB_Statistics_Admin.php on line 145

Just typed in info for a new item and when I hit the ADD ITEM button, this is the error received:
Forbidden

You don’t have permission to access /wp-admin/admin.php on this server.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.