ngcp-panel

Commit Graph

Author	SHA1	Message	Date
Kirill Solomko	dcae99bc65	TT#177851 BillingNetworks close button (back) target selection * target selection for chained routes in BillingNetworks is now performed based on the account that $c->stash->{close_target} can be already set, and it's used if defined instead of the explicit target * add NGCP::Panel::Utils::Navigation::select_back_target() * NGCP::Panel::Utils::Navigation::back_or() now uses internally select_back_target() Change-Id: If6ca47a776896db48955a04f544731dc87c59aa1	3 years ago
Alexander Lutay	1840af1eb2	TT#142402 Fix v1 'Back' button navigation on v2 (iframe inside iframe) The ngcp-panel v1 codebase uses 'back=' GET parameters to record all the navigation path and store it into the session array: '$c->session->{redirect_targets}'. On switch from v1 to v2 using the link 'GO TO NEW ADMIN PANEL', the function 'login_to_v2' is not using the concept of 'back=' GET param, but ngcp-panel still receives and stores the last value with 'empty' path: > $VAR1 = bless( do{\(my $o = 'https://x.x.x.x:1443/')}, 'URI::https' ); > $VAR2 = bless( do{\(my $o = 'https://x.x.x.x:1443/subscriber/155/details')}, 'URI::https' ); > $VAR3 = bless( do{\(my $o = 'https://x.x.x.x:1443/subscriber')}, 'URI::https' ); > $VAR4 = bless( do{\(my $o = 'https://x.x.x.x:1443/dashboard')}, 'URI::https' ); The navigation above is a recorded browsing path on v1 (in a reverse order): - login to ngcp-panel (dashboard page is opened), - open 'Subscribers' - open details for some subscriber with id 155 - open subscriber preferences - click on link 'GO TO NEW ADMIN PANEL'. As a result user is still located on the same page "Preferences", but not on v1 but v2 interface. The empty value is inserted into the array '$c->session->{redirect_targets}' (which is wrong). The empty path 'https://x.x.x.x:1443/' brakes v2 navigation for v1 'Back' button inside iframe. It causes loading of iframe inside iframe, which happens on v2 due to list of redirections: - clicking on v1 button 'back' inside v2 iframe requests https://x.x.x.x:1443/back - it triggers navigation to the top element array 'https://x.x.x.x:1443/' which is wrong/corrupted. - loading '/' cause 302 redirect to '/v2/' (as 'v2' is a default UI for mr10.0+) - loading '/v2/' inside iframe cause the issue with 'v2' content inside 'v2' iframe. This is a commit to prevent inserting an empty 'back_uri' into the session array '$c->session->{redirect_targets}'. Change-Id: I69df4320fa8cde4d23a7d9dd18ffb5eb06ee8df1	4 years ago
Rene Krenn	2537819f0d	MT#12643 billing networks and multi bill prof WIP -properly validate billing mapping intervals -api/contracts and api/customers complete +the problem with updating the "prepaid" preference remains at the moment +billing_mappings field contains future (editable) mappings only, the full schedule is given in a separate field +hal-links to all occurring billing profiles and networks -extended tests: api-customer.t and api-contract.t -api-billingnetworks.t test -billing networks panel controller +search by enclosed IP address -panel UIs for billing networks, customers, contracts +past billing mapping intervals that cannot be edited are displayed by a seperate hfh "block" part of the billing_profiles repeatable -profile packages api, UI +terminating billing profiles (MT#8645) will be broken +fixed now: profile cannot be terminated unless there are: -zero non-terminated customers, whose mappings contain the profile with future or open end -zero profile packages, that link to the profile in either one of their initial-, underrun- or topup profile sets +panel edit should work, termination wip +topup_profiles w/o amounts +contracts/customers API profile_package_id field: +apply the package's initial profiles +api/customer and api/contract profile definition modes (id/profiles/package) +api OK, api-customer.t tests +customer and contract panel UI with selector to specify actual billing mapping, schedule or profile package (same as api) +terminate logic harmonized: profiles, networks, packages +api tests updated +prepare for merging: cleanup, enable tests Change-Id: I6c0dec72f490b5731fc673cd393d6aeb08dd8143	10 years ago
Andreas Granig	88bcc049f5	MT#6731 Remove "back" param from form if posted. Somehow this sneaked in from somewhere and so far only happens with resellers, so make sure to just clear it if a form got posted.	11 years ago
Andreas Granig	05553d0406	MT#4413 Remove debugging messages. This even breaks domain creation for PBX.	12 years ago
Andreas Granig	dd62516857	Fix $controller::auto declaration.	12 years ago
Andreas Granig	d801311821	Remove debug output to stdout.	12 years ago
Andreas Granig	e770783788	Fix navigation and CF handling. Old CF handling didn't work with Firefox due to some auto-focus issue with our HTML code in the URI/timeout fields.	12 years ago
Andreas Granig	01b3856ee7	Align domain handling to new DT mechanism. While we're at it, show reseller domains in reseller details.	12 years ago
Andreas Granig	e1f7a4710e	Properly handle back button.	12 years ago
Andreas Granig	21af84fdf6	Lots of cleanups and bugfixes and back-nav. Implement automatic back navigation. Fix subscriber creation. Unify controller handling.	12 years ago
Andreas Granig	04296de4c4	First part of reworking reseller handling.	12 years ago
Andreas Granig	0b37392f54	Enhance navigation. Simplify back-uri for navigation utils calls. Start using back_or navigation utils function for auto-checking close-targets. Move navigation stack check into auto of each controller.	12 years ago
Andreas Granig	4b3d1caab6	Streamline forms in regards to submitid.	12 years ago
Andreas Granig	f996d4a15e	Move naviation to NGCP::Panel::Utils::Navigation	12 years ago

15 Commits (master)