Also tried to uninstall the plugin, shut down, restart, reinstall, reimport, and nothing seems to restore the [quotes=llama] functionality. Also tried it on multiple PCs to be sure nothing was cached that might be the issue, no help.
-
This reply was modified 2 years, 5 months ago by
hawkeeye.
Hawkeye,
Working on this… get back to you asap.
Updated to 1.3.6 which should fix the [quotes-llama] not showing. Let me know how this affects the database error. I am unable to produce the “table missing or corrupted” error and am wondering what is happening there.
Let me know.
I am getting my provider to do a restore to yesterday, but I did the 1.3.6 update and the functionality for that one option still does not work.
I think this is the simplest one, so I don’t get it. The other options work as intended, but not this basic option
The import function definitely does not work for either csv or json files. The plugin seems to just hang and never advances unless this should take a long time. The file is only about 300 quotes and my systems are large, so resources are not an issue.
Before you waste a ton of time let’s get the restore done. Hopefully I have not lost the data.
I somewhat have recovered
The [quote-llama] function works on 1.3.4 but I am concerned about going to 1.3.6 until I know it works
Another BIG issue is that the export to CSV did not work with long quotes and the import kept failing because the file data was just messed up
I manually went in and fixed the file and then the import worked quickly and well
I will be happy to make the before and after CSV file available to you if it will help you
It appears that it did not handle punctuation correctly and kept splitting quotes when it encountered a comma, quote, or other mark
Sure! Send me a link where I can grab them and I’ll see what I can make of it. So far, I am not having any issues testing on my side the import/export.
I’d also ask anyone else in the WordPress community that is reading this and having this type of problem to please chime in?
Unfortunately I don’t have a link, but I can attach them to an email and send them if you can give me an email link
By the way, thanks for the support and for hanging in there on this issue. It is becoming rare and it is appreciated.
-
This reply was modified 2 years, 5 months ago by hawkeeye.
You can send to:
llama at oooorgle dot com
I was able to add your quote example as a new quote and the export and re-import succeeded without any issue as well (using 1.3.6).
From which file, I sent three
1 – The bad Json export
2 – The bad CSV export
3 – The CSV that I corrected from 2 manually
Also, did it work with 1.3.6 and shortcode [quotes-llama]?
If I have to get my provider to rebuild again I will have to pay
Since 1 and 2 came directly from an export do you know that we can backup our files with the built in export?
-
This reply was modified 2 years, 5 months ago by hawkeeye.
I had not tested the corrected file…
1 – The bad JSON successfully import – 263 quotes imported. Successful export and re-import.
2 – The bad CSV successfully imported – 272 quotes imported. Successful export and re-import, though has several empty entries.
3 – The corrected CSV successfully imported – 263 quotes imported. But with parsing issues – Entries starting and ending with double-quotes are inserting all fields into the quote field, leaving the remaining fields empty.
-
This reply was modified 2 years, 5 months ago by
oooorgle.
Well I am not sure what the difference was
on 1.3.6 the import of the exported file failed
Same with the JSON file
With both the system just hung
So I manually straightened out the exported CSV and it imported fine into version 1.3.4
AND the [quotes-llama] functionality was fine
I think I will let the new release sit for a week or so and see if anyone else has issues before I update
Thanks for all the help
