Issues with FrontEndUsers & Uploads Modules on v2.0

[mr.bacan]

Hi, I recently installed a fresh copy of CMSMS 2.0 and started to face a couple of issues using FEU and Uploads Module.

FEU 1.30.4
Issue #1
It shows up the login form perfectly but when logged in it just doesn't redirect to the proper page, even though it is configured on "Redirection Settings", the login form keeps showing as if you've never logged in. When you try to access again, it says "The user is already logged in".

Issue #2
Even if not logged in, if I type the page link directly, I get access even though the page type is a "Protected Page" and only a certain group has the permission to access it.

Uploads 1.19.4
Issue #1
Files are set to be visible only to a specific FEU group, but it's not working. Anyone with the correct link can access the files, no matter if logged or not.

Issue #2
On the "Reports" tab if try to get a report it shows this message "The FrontEndUsers module (version 1.21.15 or greater) is required for this operation", but I'm using version 1.30.4

So far these are the issues I've been facing. I've used FEU and Uploads on previous versions of CMSMS without any issues. Don't know if it's something I'm doing wrong or there's an actual error.

On previous versions of CMSMS I used to use CustomContent which is deprecated on v2.0, so don't know if that has anything to do.

Thanks in advance for any help on this.
----------------------------------------------

Cms Version: 2.0

Installed Modules:

CMSMailer: 5.2.4
AdminSearch: 1.0
FileManager: 1.5
MenuManager: 1.50
MicroTiny: 2.0
ModuleManager: 2.0
News: 2.50
Search: 1.50
ThemeManager: 1.1.8
Captcha: 0.5.2
CGExtensions: 1.49.7
CGSmartImage: 1.20.3
CGSimpleSmarty: 2.0.1
FrontEndUsers: 1.30.4
AdminIPLock: 1.0
Uploads: 1.19.4
TinyMCE: 2.9.12
CMSContentManager: 1.0
DesignManager: 1.0
Navigator: 1.0


Config Information:

php_memory_limit:
max_upload_size: 2000000
url_rewriting: mod_rewrite
page_extension: .html
query_var: page
auto_alias_content: true
locale:
set_names: true
timezone: America/Panama
permissive_smarty: false


Php Information:

phpversion: 5.4.42
md5_function: On (True)
json_function: On (True)
gd_version: 2
tempnam_function: On (True)
magic_quotes_runtime: Off (False)
E_STRICT: 2048
E_DEPRECATED: 0
test_file_timedifference:
test_db_timedifference:
memory_limit: 64M
max_execution_time: 60
output_buffering: On
file_uploads: On (True)
post_max_size: 8M
upload_max_filesize: 2M
session_save_path: /tmp (0700)
session_use_cookies: On (True)
xml_function: On (True)
xmlreader_class: On (True)


Performance Information:

allow_browser_cache: Off (False)
browser_cache_expiry: 60
php_opcache: Off (False)
smarty_cache: Off (False)
smarty_compilecheck: Off (False)
smarty_cache_udt: Off (False)
auto_clear_cache_age: Off (False)

Server Information:

Server Api: cgi-fcgi
Server Db Type: MySQL (mysqli)
Server Db Version: 5.5.42
Server Db Grants: Found a "GRANT ALL" statement that appears to be suitable
Server Time Diff: No file system time difference found


----------------------------------------------

[leoteo]

Hi mr.bacan,

just concerning issue #1 in FEU - this is due to a typo in the FEU module, which you can fix easily yourself (and is promised to be fixed in future releases). See the bug report.
You might want to have a look through the bug reports on the cmsms forge also concerning your other issues and maybe file them as bugs there.

Cheers
leoteo

[calguy1000]

Your FEU Issue #2 was related to a change that was done in 1.11.something and didn't make it's way into 2.0 at the time.

It's fixed now, and will be available in the 2.0.1 release coming soon.

[mr.bacan]

concerning issue #1 in FEU - this is due to a typo in the FEU module, which you can fix easily yourself (and is promised to be fixed in future releases). See the bug report.

Thank you so much leoteo, that solved this specific issue.

[mr.bacan]

Your FEU Issue #2 was related to a change that was done in 1.11.something and didn't make it's way into 2.0 at the time.

It's fixed now, and will be available in the 2.0.1 release coming soon.

Thanks Calguy, looking forward for an update. Is there any workaround in the meantime?

[calguy1000]

In the mean time you can use the feu_smarty::get_current_userid() method.
which replaces the CustomContent stuff.

It's uglier than the protected content page, but it should work just fine.

[mr.bacan]

In the mean time you can use the feu_smarty::get_current_userid() method.
which replaces the CustomContent stuff.

Hi Calguy, thanks so much for the tip. I ended up using feu_protect instead since I didn't knew how to implement it properly