[Resolved] js bug
Okay, thanks! I’ll fix it.
Update: Fixed in development version (trunk)
You’re welcome, there’s more coming — thanks for your hard work.
Not sure if this is a result of me deleting actual files and folders first — in the current version, if I trash some folders, then either “empty trash” or select all then “delete permanently” – all trashed folders resurrect in the filesystem and appear as published
Trashing and deleting (multiple) folders is something I’m working on.
The trashing procedure is quite tricky.
If a folder has subfolders it will not delete permanently.
So, if you want to delete multiple folders, the script has to find the deepest subfolder first and start deleting upwards.
If deleting the folder on your server fails, it will be ‘found as new’ the next time you open the All folders page.
Permanently deleting a single folder should work now (in trunk).
I’ll test multiple folders/empty trash later.
Hey, I’m not sure if this is the same issue, but on the widget the tree structure gets added another level which makes all links broken.
Example: if the gallery folder is /images/ it creates /images/images/image.jpg
so all images are broken.
for example the image is in http://www.fucagua.org/wp-content/uploads/fotos/laguna-de-guimoreto/Laguna-de-guaimoreto-_DSC8451-W1200.jpg
but the img source tries to get it on
this extra /fotos/ level gets added for all images!
If I create another folder and move all others to /fotos/ I’m afraid I’ll get the all indexed again as duplicates.
PS Your plugin will solve so many issues large gallery site have! thanks again
please supply a link to your gallery folder.
If your gallery root folder is wp-content/uploads/fotos/, you have to make a folder in there to show your images.
I did, I have 83 folders on the /fotos/ folder.
So I created the folder via ftp, then I installed the plugin and set the http://fucagua.org/wp-content/uploads/fotos/ as the root, then I uploaded all the folders containig the pictures so the url would be fucagua.org/wp-content/uploads/fotos/cyathea-costaricensis-tree-fern-helecho-arborecentes
but then when the images show they are all broken, as the url for each image is http://www.fucagua.org/wp-content/uploads/fotos/fotos/cyathea-costaricensis-tree-fern-helecho-arborecentes/#imagename#
If I go to the database and find replace the /fotos/fotos/ for /fotos/ could this problem be solved?
I don’t know if the
fotos/fotos/is in your database.
Would like to see it for myself. I’ll see if I can reproduce this error.
I just checked the database, all url for the
wp_postmeta start with fotos/… (all ftp uploaded images are like that)
so the plugin adds the fotos/ as the root folder and then the media adds the fotos/imagefolder/imagefile
Just to make it work I’ll replace all fotos/ for nothing, so I can show the images right.
Just as a note, I installed laziest first, then did an upgrade and it said terrible error or something like that.
Then I uninstalled the plugin and installed eaziest again ( and deleted folders, and moved folders around, and… everything that could make it go wrong 🙁
I’m more than willing to give you access to my database or send it to you if it helps!
If you’ve got a message like
Something went terribly wrong in the upgrade process. Please check your settings above.
You probably had the wrong path to your Gallery. Eazyest Gallery will not import if you don’t set the folder right. This is to prevent you from importing system folders or something like that.
Please check if your Gallery folder in Eazyest Gallery Settings is
wp-content/uploads/fotos/indeed. If so, removing the
fotos/from all records with
meta_key = _wp_attached_filein wp_post_meta could do the trick.
Also, do you use any other image related plugins?
yes I use these plugins (have them installed, but don’t use them):
Faster Image Insert
Scissors and Watermark
Watermark RELOADED (deactivated)
the gallery folder is wp-content/uploads/fotos/
I’m trying to replace the /fotos/ in the database, either I kill my website or fix the problem. Hope it’s the second one.
- The topic ‘[Resolved] js bug’ is closed to new replies.