I need help - issue with my move from local to my host

[BillyBoy0823]

I am moving from my local host to my Host site. I was able to get it close to working, but had a little trouble. The site is Mostly working. but in the Admin, there are no top icons, and clicking where they should be does nothing.

Here's the things I've done,

Loaded another site elsewhere to get a fresh Database. It worked fine installing it At the host.
I copied that db and I still get the same issue.
I changed themes, and that didn't change it.
I can go to SOME of the links directly, ie;

-- fileinspector.php - but it won't let me run it.

• • prefs.php - this works - but I see ALL the prefs on one page.
• • db.php works - I ran and it says core is ok, plugins OK too

Not only can't I click on the spaces, but buttons are just black.

That Vs a fresh install, where it all works and I see the icons, and buttons work.

I can't figure out where the issue is. Other than not having a fully working Admin area the site is running well. I am excited to get it going after 16 hour coding days since Feb :) Not sure if I should share link.

Any pointers? TIA!

[BillyBoy0823]

I ended up doing it all from scratch, although I still wanted to find out why? When I went through all the core prefs, I found something very confusing. Not sure if it belonged, but it was a WP link. I am starting to think my DB got corrupted first time around.

Any ways, I'm on my way!

[e107help[bot]]

@BillyBoy0823, glad you're out the other side, and good instinct to want the why anyway.

Quick version: the database wasn't corrupt. Black buttons, no top icons, every Settings tab stacked on one long page, and a fileinspector that loads but won't run, that whole cluster is one fault wearing four hats: the admin's CSS and JavaScript never reached the browser. No stylesheet and the buttons render as bare boxes while the icons vanish; no JavaScript and the tab panels can't fold away (so you get all of them at once) and nothing answers a click. db.php and prefs.php "worked" because they still build server-side, they were just standing there naked.

Why it shrugged off a fresh DB and a theme swap: it's a files thing, the database was never the cause. The admin's libraries (Bootstrap, jQuery, Font Awesome) live under e107_web/lib/, a deep nest of hundreds of tiny files, and that's exactly the bit an FTP run from XAMPP likes to half-finish or skip. A clean install lays e107_web/ down whole, which is why the from-scratch one came up perfect.

Next time you won't have to guess. Open the browser dev tools (F12), Network tab, reload the admin page, and watch for red 404 lines on anything ending .css or .js. Those are your missing files, named and pathed, right on screen (so no, you don't need to share your URL for it).

On that "WP link" in the prefs: a stray URL sitting in a setting wouldn't black out the admin chrome, so I'd not hang the corruption theory on it. If it's still nagging you, tell me which pref key it was in and I'll tell you what it actually does.

16-hour days since Feb and you're nearly home.

[Jimmi08]

If this happens again, check Console (F12/ second Tab) - you would see there what css or js is causing the issue and see the path to fix it. If there is no red warning, the issue is somewhere else. Sometimes you need to clear the cache (browser + e107 cache folder)

[BillyBoy0823]

Thank you! Glad to know what caused it. I have enough things I don't understand :)

As for the wp thing, I just saw it when I was dissecting the db after the move from one to another. Because there are installs for all sorts of stuff in Cpanel, I thought maybe my host's db or site had issues;

Here's what I saw that seemed out of place;

INSERT INTO xyz_online (online_timestamp, online_flag, online_user_id, online_ip, online_location, online_pagecount, online_active, online_agent, online_language) VALUES (1781392732, 0, '0', '2a06:98c0:3600:0000:0000:0000:0000:0103', '/wp-admin/install.php?step=1', 1, 0, 'http://zyzmysite/wp-admin/install.php?step=1', 'en'),

And, while you asked, here's the only issue i found during my install from scratch. In;

/e107_admin/admin_log.php?mode=main&action=maintenance

ADLAN_155 was not defined.

Do you want me to report it elsewhere? Let me know...

Thanks again, Both of you ;)

[e107help[bot]]

@BillyBoy0823 mystery solved, and it's good news: nothing's corrupt.

That xyz_online row is e107's who's-online tracker doing its job. online_location records "the page each visitor last requested", and a bot requested /wp-admin/install.php?step=1 on your site. That's the most common automated probe going: scanners spray /wp-admin/install.php at every site they find, fishing for a half-finished WordPress. e107 logged the hit, the bot moved on, your DB is fine. The cPanel one-click installers on your host aren't leaking into it, it's just the background noise every public site gets.

(@Jimmi08's Console tip is the other half of the same F12 trick: Network shows you the 404, Console names the file that asked for it.)

On ADLAN_155: let's not call it a bug just yet, because I can't make it misbehave from reading the code. It's only the "System Logs" label, and on a standard English install it should always be defined on that page, so something about your particular setup is tipping it over and I'd like to find out what. A few answers would narrow it right down:

• where exactly did "ADLAN_155 was not defined" show up? A blank or red error page, or a line in the log list itself?
• which PHP version is the host running?
• is your admin language set to English, or something else?
• does it happen on the other tabs of that page too (list / audit / rolling), or only on the maintenance screen?

Tell me what you can and we'll work out together whether it's a real bug or just a quirk of your install. Good eye for catching it either way.

[BillyBoy0823]

where exactly did "ADLAN_155 was not defined" show up?
It is under System logs - all choices but the 2nd one. Sorry, should have been more specific.

[e107help[bot]]

@BillyBoy0823 I built a clean install and went hunting, and I couldn't make it misbehave, which is the good news: on a fresh site every System Logs tab shows the right "System Logs" heading, and when I deliberately knocked that label out, every tab broke the same way, never just some. So the label itself is sound in core, and whatever bit your copy was specific to it.

The thing that'd actually pin it is your PHP error log, it writes down the exact file and line that choked, assuming the reinstall didn't wipe it. On cPanel it's under Metrics → Errors, and you'll often also find an error_log file sitting right in the folder (worth a look in your site root and in e107_admin/). You're after a line mentioning ADLAN_155, something like Uncaught Error: Undefined constant "ADLAN_155" in .../admin_log.php:NNN. Paste that and it'll tell us exactly what tripped.

If the log's already gone, no drama: my bet is a file that didn't upload whole (e107_languages/English/admin/lan_admin.php or admin_log.php), or a stale server cache holding one. Re-uploading those and clearing any opcache your host offers should sort it.

[BillyBoy0823]

OK, So, I uploaded 3 times, twice via filezilla and once as a tar, and actually unzipped it there then in stalled it.

All three installs show the same error. No big deal, just want ya to know I'm not krazy :)

I am using default theme
I cleared cache
I cleared my computers cache, windows temp, firefox cache's

No idea why one would show fine, and the other options show the ADLAN_155. I thought maybe someone just typed in "System Log and planned to come back to it later, so that one appears.

I DID check Languages, and it IS defined. In fact I added it again got a duplicate error.

I also turned on debug basic and got this guy'
Undefined array key 1, Line 20 on xxxx/e107_languages/English/admin/help/admin_log.php

This is all on a 2.37 in case you were wondering...

Hey, it's minor and it works :)

[Deltik]

Hey @BillyBoy0823, @e107help had been trying to reproduce your issue on the latest master revision and didn't realize that you hit a bug that wasn't fixed in the e107 v2.3 tree.

c9575b2 is what would fix the ADLAN_155 bug, but it wasn't included in e107 v2.3. It is indeed fixed in the latest of the master branch.

It's getting very hard to maintain e107 v2.3 now, so I'm pivoting my efforts to getting e107 v2.4 ready. I can't spend too much time on small cosmetic issues anymore, so that ADLAN_155 glitch will have to stay until the big feature release.

P.S. That Undefined array key 1 warning you were getting was still a bug in master, so #5773 fixes that.

[BillyBoy0823]

I completely, understand. I am still asked to look at 20 y.o. crap. I want to move on.

I just thought I should post issues I come upon, and let you decide. It will take me a while to catch up.

Thanks for all your hard work. I look forward to 2.4 :)

[Deltik]

Thanks for your patience, @BillyBoy0823. You have indeed been bringing up legitimate issues, so please keep doing that!