kiess

yeah, what you showed in your screenshot is what it does for me too — shows the box correctly but doesn’t fade in, and doesn’t show the transparent gray background behind it anymore like it used to (the one that covered the rest of the content on the page). any idea how i might fix that? as i said, for some reason it’s not changing the “display:none” property on that gray background (while it does change it on the agreement box itself), so it just doesn’t display. i couldn’t find where in the code it controlled that property to try and fix it.

thanks a lot for replying.

so how did you get the test to work? no matter what browser i use i just see the disclaimer box itself without the gray background that covers the rest of the screen (and there is no fade). you are seeing the gray covering the screen behind the agreement and it fades in?

i can’t change templates because it’s a client’s site. i tried copying the contents of agreement.js to the footer.php file as well, but that didn’t seem to do anything.

i tried removing my calls to the mootools files as well, but i got the same result. also tried reinstalling agreement altogether — same result. ??

any other ideas you have are appreciated! thanks much.

just to update: it appears that the back layer isn’t changing the “display:none” setting for some reason. i got the main box to move up where i want it in the css, but yeah something is broken with the fading in of the back gray layer.

so i have a positive update — i think i finally figured it out.

i did another fresh install (4 of them, actually) because i was hellbent on figuring out exactly what caused the errors.

i did an import of old posts from a Blogger blog and everything worked fine and it still let me add posts.

i did an import of old posts from another WordPress and that also worked fine and let me add posts as well. so far so good.

then i tried Tumblr, and guess what? it broke again — instantly. every post says “submit for review” instead of “publish” and i can’t do anything.

i started thinking maybe the export tool that i used for Tumblr somehow corrupted the .xml file i was importing. so i found and used a different export tool, which is here: https://www.tumblr2wp.com/ it generates a wordpress compatible xml file from your tumblr blog and you import it using the wordpress importer.

guess what? it works.

all my old posts are now onsite and i still seem to have admin privileges somehow. so i don’t really know what happened or why it’s working, but maybe some Tumblr exporters corrupt the file and thus corrupt your install somehow. either way it seems to be working now — knock on wood.

hope this works for someone else.

i don’t think this is the same issue for me/the rest of us. my server (godaddy) sets up the database and user automatically to work with wordpress, and i’m not sure i even see a place in their control panel to change the privileges of a database user (there is only one, after all). on top of that, the whole thing works on a fresh install before you try to import old posts — if it was a user privilege issue i feel like nothing would work on a fresh install either.

anyway, curious if anyone else tries this and if it works for them.

yeah i can do a fresh install as well even on my hosting server and it works fine — it’s when you import old posts that everything seems to corrupt and fall apart. i don’t get it. but i need old posts so we have to figure this out one way or another.

chuffer – the db version is a line in the wp_options table (there are about 220 rows in there and i didn’t see it on the first page). when you hard change it to an old number and refresh your wp admin page it sees it’s out of date, updates it, and you’re set. unfortunately that didn’t change anything.

i’m not too happy at the moment either – i picked wordpress for its ease of use and i’m already several weeks behind schedule because of bugs…

h-e-l-p.

well just fyi in regards to Esmi’s link and some of its suggested solutions:

– just tried the forced database upgrade and that didn’t do anything – same problems.

– commenting out a certain string in the wp-settings.php file was a no go too, as the string in question doesn’t even seem to exist in the latest version of the wp-settings.php file.

– i tried updating the table names (changing “wp_user_roles” to “wp_new_user_roles” etc) and that actually made me unable to even log in to wordpress at all.

so this appears to be yet another link that doesn’t contain any actual viable solutions. feel free to double check me but i think those were the main 3 suggestions in the thread.

yeah i’m dead in the water too until someone can help narrow this down….

so maybe it has to do with the importing of xml files in some way…does that help any moderators to shed any light on the issue?

anyone else have any ideas on this?

yeah i read those before posting – no luck there. i searched for the table row he mentioned but it wasn’t there; and the other link in there someone links to is about 4 years old and doesn’t seem relevant.

i think your two links are the same, actually.

linux server, yeah.

same issue with a new user; creates successfully, logs in successfully, but same errors.